Rails Performance First Aid
summary
Shows concrete fixes: use New Relic or Skylight and flamegraph profilers to find hot spots (one app drops from 6 seconds to ~500 ms after fixes), run load tests before/after, and aim for ~250–300 ms end-to-end. Remove Ruby-level work by adding joins or SQL NOT EXISTS queries, fix N+1s with Bullet and the undocumented preloader trick, add partial indexes and EXPLAIN plans, move servers closer to users to cut network latency, and use fragment/JSON caching with Redis and conditional GETs (304s).
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:03Rails performance myths
- 5:04First aid approach
- 11:16Measuring performance
- 16:57Database tuning basics
- 25:30Caching strategies
- 28:37Quick optimizations
- 30:06Summary and Q&A
related talks
26mRails Performance Monitoring 101: A Primer for Developers
30mRails Performance monitoring: A primer for developers
45mRails Performance Monitoring 101: A Primer for Junior Developers
01h 02mPerformance
35m"10 performance sins of Rails applications"
42m3x Rails: Tuning the Framework Internals
44mPanel: Performance... performance
01h 15mSpeedupRails, Speedup Your Code
