Slow database in your PHP stack? Don't blame the DBA!
summary
Typical slow requests turn out to be application problems: tight loops produce N+1 query loop behavior that fires hundreds or even 500× more SQL calls per page, missing or misused indexes force full scans, and sending non‑bind statements defeats the DB statement cache and spikes CPU. Concrete fixes: collapse queries, add the right indexes, switch to bind parameters, and verify with EXPLAIN plan and a transaction tracer (Dynatrace or similar) to see actual statement counts, execution times, and whether the change reduces DB load.
AI-written summary · about
chapters (40)
- 0:00Introduction
- 2:50Story
- 3:15Performance issues
- 3:33In the operation department
- 4:56Central Locking
- 5:10Timestamp Capture
- 5:25Load data
- 5:38Database performance
- 5:49Slow queries
- 6:06Blame game
- 6:18The problem
- 6:54Database performance hotspots
- 7:35Why is most time spent in the database
- 7:54Slow database queries
- 8:24Too many database queries
- 8:37Exercise
- 8:47ORM vs Hibernate
- 10:54Recall
- 11:13Database statements
- 11:39One query
- 11:59SQL
- 13:26Where clause
- 13:38Database load reduction
- 14:14Caching
- 15:05Query Cache
- 19:17Database Metric Dashboard
- 19:54How could that be done differently
- 20:26CPU usage
- 21:09Using indexes
- 22:04What are indexes
- 22:14What is an index
- 23:32Using a different column
- 24:21Indexes
- 25:47In clause
- 27:33Developer perspective
- 27:56Performance is essential
- 29:07Selfsufficient developers
- 30:53Single select statements
- 32:27Key takeaways
- 34:17Questions
related talks
45mPHP's biggest bottleneck, MySQL
35mDatabase Stalls, From the Ordinary to the Obscure
31mNo more slow requests
41mUsing Databases to Pull Your Application Weight
50mSupercharge your Code to Get Optimal Database Performance
54mBottleneck Analysis
49mHELP!!1! The database is slow!!
31m"Optimizing SQL Queries"