Database Highload: When to Scale and When to Optimize
summary
Shows how to decide between scaling and optimizing using concrete metrics (CPU%, requests/sec, disk latency/IOPS, cache life) rather than buzzwords. Describes capturing queries with extended events into a table (example: highload) to group by text and find hot spots, then profiling a slow stored procedure (transaction_history) that took 69s vs others at 12s and cutting its cost by ~90% through targeted optimization. Also warns that SAN drivers or network latency can introduce random 1–30ms disk I/O spikes that affect performance.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:10Why databases slow down
- 3:40Scalability markers
- 7:30When scaling fails
- 10:44Diminishing returns in scaling
- 13:18Memory and caching issues
- 16:08Disk load and latency
- 21:13Cloud vs bare-metal scaling
- 24:28Finding load sources
- 25:53Query tracing demo
- 30:26Query optimization and load balancing
- 35:27Scale or optimize decisions
- 36:52Optimization vs scaling takeaways
- 38:39Q&A
related talks
47mMy Database Can't Handle the Load. What to Do?
49mHighLoad Solutions On MySQL
49mHighLoad Solutions On MySQL
49mHighLoad Solutions On MySQL
58mTroubleshooting CPU Performance Issue for SQL Developers
53mOptimizing your Azure SQL Database workloads
54mPerformance Analysis and Optimization of MySQL
10mBuilding High-Performance Financial Data Pipelines
