How MySQL Configuration Tuning Boosts App Performance
summary
Research runs real-world apps (Drupal Commerce, Laravel stores, WordPress, PrestaShop) on EC2 with JMeter-driven workloads and compares default vs tuned MySQL/MariaDB configs; no application code changes but up to 63% and 97% latency reductions depending on DB size (1–5 GB), CPU drops and QPS increases follow, and results live on published metrics and GitHub. The most impactful change is innodb_buffer_pool_size set to ~60–70% of RAM and tuning consistently yields immediate, reproducible gains.
AI-written summary · about
chapters (14)
- 0:00MySQL tuning intro
- 1:54Opportunities to improve application performance
- 3:45Default config limits
- 5:30Tuning impact research
- 8:08Drupal 1GB results
- 9:55Drupal 3GB results
- 11:02High latency root cause
- 12:26IMIOS tuned testing
- 13:53WordPress perf gains
- 15:39PrestaShop tuned perf
- 17:05Results summary
- 17:47Tuning learnings
- 18:50Safe tuning start
- 20:41Q&A
related talks
16mWhether tuning MySQL configuration important?
53mMySQL DevOps
53mIntroduction to MySQL Performance Tuning - workshop 1hr
43mOptimizing MySQL without SQL or touching my.cnf
56mOptimization Techniques in MySQL
57mPerformance Analysis and Optimization of MySQL
54mPerformance Analysis and Optimization of MySQL
41mMySQL Performance for DevOps