Efficient MySQL Performance
summary
Argues that MySQL performance equals query response time and gives concrete steps: enable low-latency metrics (preferably 5s or better), run pt-duplicate-key-checker, use performance_schema.data_locks to inspect InnoDB locking, explain and optimize slow queries, and monitor replication lag (treat >1–2s as serious and page on alert, aim for sub‑sec measurements where possible). Recommends planning sharding/ops around ~2–4 TB per instance and warns cloud network‑backed storage adds ~1 ms latency.
AI-written summary · about
chapters (18)
- 0:00Start
- 9:55Query Response Time
- 11:48Improving Mysql Performance
- 15:21Indexes and Indexing
- 19:01Indexes Provide Leverage against Data
- 19:16Why Indexes
- 20:45Explain Slow Queries
- 21:22Data Storage and Access
- 25:30Action Items
- 26:06Consider a Different Data Store
- 26:34Sharding
- 29:27Server Metrics
- 33:20Insight Is Proportional to Your Metric Resolution
- 35:00Replication Lag
- 38:58Nodb Locking
- 43:50Review the Code
- 44:06Abandoned Transactions
- 51:10Database Operations Manual
related talks
53mMySQL DevOps
34mMySQL and InnoDB Performance for the Rest of Us
54mPerformance Analysis and Optimization of MySQL
57mPerformance Analysis and Optimization of MySQL
53mIntroduction to MySQL Performance Tuning - workshop 1hr
49m18 Ways to Fix MySQL Bottlenecks
21mWriting High Performance SQL Statements
56mOptimization Techniques in MySQL