MySQL DevOps
summary
Focus on practical MySQL tuning for high-load systems: prioritize hardware and InnoDB settings (buffer pool, storage, network, temp table sizes ~32MB min) because about 5% of settings yield ~95% of gains, and configure replication carefully (readonly replicas, skip-start) while validating backups and restores. Use ProxySQL for routing, PMM and Grafana for monitoring, offload long read/report queries to a separate replica, disable MySQL query_cache in favor of Redis/Elasticsearch for caching, and weigh RDS/AWS tradeoffs and noisy-neighbor risks.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:58MySQL needs DevOps
- 10:37Scaling challenges
- 15:18Modern cluster config
- 21:46Killer queries
- 29:03Monitoring and load
- 34:35Server to cluster
- 40:09Cloud solutions
- 43:50Cloud limits
- 46:20Q&A
related talks
41mMySQL Performance for DevOps
53mIntroduction to MySQL Performance Tuning - workshop 1hr
25mMySQL Performance for DevOps
47mThe Low Hanging Fruits of MySQL
54mPerformance Analysis and Optimization of MySQL
57mPerformance Analysis and Optimization of MySQL
56mOptimization Techniques in MySQL
35mBest Practices for MySQL Performance
