Holistic Database Application Tuning
summary
Database changes reduce hundreds of per-page queries to one by turning Ruby methods into a single data‑set method backed by Postgres; logs from PG Badger show a primary‑key select running 10–13 million times daily and costing hours until replaced. The team implements set‑returning functions and a package‑style script (a 380‑line function plus refactored pieces), getting a measured 4x speedup on hot methods while preserving application logic.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:31What is a holistic application tuning?
- 3:57What is the most common complaint of app developers ?
- 8:26How Active Record works
- 11:58The sketch of proposed changes
- 13:17Logic Split methodology
- 16:11Modified method
- 16:26Matching SELECT
- 21:59Package example
- 32:42Advantages
related talks
01h 01mNew Approach to Resolve objectrelational impedance mismatch
31mUsing Databases to pull your applications weight
41mUsing Databases to Pull Your Application Weight
30mPuny to Powerful PostgreSQL Rails Apps
41mOptimizing your app by understanding your PostgreSQL database
27mPostgres Performance in 15 Minutes
43mOptimize Python & Django apps with Postgres superpowers
31m"Optimizing SQL Queries"