Database Performance at Scale for RoR Applications
summary
Ruby on Rails apps hit real limits: Active Record’s “auto‑magic” causes duplicated and slow queries, and GitHub runs this at 60 million users with 19M repos and 15M issues. Expect concrete fixes: finding n+1 queries with request‑level instrumentation, measuring raw query counts and latencies, adding focused MySQL indexing optimization, cloning production tables to staging to validate plans, running A/B query experiments, and capping database round trips and pagination.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:26Why is performance important
- 1:00Why performance matters
- 2:15Numbers
- 3:00Graphing
- 3:40Customization
- 4:11Common Problems
- 5:03Pig
- 6:25Poor Indexing
- 6:50Too many indexes
- 7:39Postgres
- 8:28Multicolumn index
- 9:02Extend existing index
- 9:30Exception tracking
- 10:51Hebert
- 11:25Science
- 12:19Limits
- 12:40Summary
- 13:07Thank you
related talks
31mA Rails performance guidebook: from 0 to 1B requests/day
29mA Rails Performance Guidebook: from 0 to 1B requests/day
26mRails Performance Monitoring 101: A Primer for Developers
01h 52mBuild High Performance Active Record Apps
01h 52mBuild High Performance Active Record Apps
29mScaling Rails to 2M MySQL requests per second
31mA RAILS PERFORMANCE GUIDEBOOK
01h 03mRuby at Scale