On API Optimization
summary
A live API goes from ~5000 ms average to sub‑1s by following a strict workflow: get a baseline, profile with New Relic and a local object profiler (stackprof style), inspect DB with a SQL query tracer, find one application method repeatedly calling an external Google currency conversion, and replace it with a cached lookup and a single DB result. The fix includes added tests, load checks and regression monitoring and measurably cuts median and p95 latencies to acceptable levels.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker background
- 1:14What is API optimization
- 3:09Understanding API structure and bottlenecks
- 5:18Finding the root cause of API slowness
- 7:30Tools for profiling and monitoring APIs
- 10:45Profiling with New Relic and other tools
- 12:54Common performance pitfalls and quick wins
- 15:24Avoiding major changes for minor gains
- 16:50Library performance and third-party dependencies
- 19:52Testing in production and pre-production
- 21:23Automating performance checks
- 23:15Case study: Currency conversion API
- 26:15Summary and key takeaways
related talks
29mYour API is Too Slow!
43mAPI Optimization Tale: Monitor, Fix and Deploy (on Friday)
30mRails Performance monitoring: A primer for developers
26mRails Performance Monitoring 101: A Primer for Developers
24mAPI Optimization Tale: Monitor, Fix and Deploy
17mHands-On Experience in API Performance Testing | What is API Testing
29mAccelerate API Innovation: Secrets to Staying Ahead
31mHigh performance APIs in Ruby using ActiveRecord and Goliath
