"10 performance sins of Rails applications"
summary
Shows specific fixes and measured results: set up New Relic/Skylight/Datadog and track mean, median and 95th percentile; move a preloaded 2000 stations live-search from front end to backend and cut initial page load ~20% with a ~3% conversion lift; removing one unnecessary Facebook Pixel yields ~50% speed increase; use pluck/select/count and add DB indexes to avoid heavy ActiveRecord objects; push email/report work to background using Active Job / Sidekiq and enqueue IDs not objects; test on slow phones to catch front-end bloat.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:36Measuring performance is key
- 7:04Front-end vs back-end speed
- 11:08Optimization without measurement
- 15:34Doing too much in code
- 18:45Caching strategies in Rails
- 20:13Active Record performance pitfalls
- 27:12Offload work to background jobs
- 31:40Front-end performance matters
- 34:00Q&A and closing
related talks
32mRails Performance First Aid
26mRails Performance Monitoring 101: A Primer for Developers
01h 02mPerformance
30mRails Performance monitoring: A primer for developers
45mRails Performance Monitoring 101: A Primer for Junior Developers
48mOn the Edge of Rails Performance
44mPanel: Performance... performance
58mPanel Discusion - Performance problems in Rails applications
