Whether tuning MySQL configuration important?
summary
Compares default versus tuned MariaDB on EC2 (Debian 11, 4 cores, 5 GB RAM) running Drupal Commerce Kickstart and Laravel stores, using 10-minute JMeter runs via BlazeMeter with datasets of ~3 GB and 500 MB. Tuned configuration yields 63% latency reduction in one test and 42% in another, cuts CPU peaks (defaults hit ~100%), and raises throughput to about 2x queries per second. Results come from repeated deploy → baseline test → apply tuned my.cnf → retest.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:32Background
- 1:03Agenda
- 1:35Opportunities to improve performance
- 2:53Research
- 3:54Testing
- 5:29Drupal Commerce
- 6:20Latency
- 6:52Queries per second
- 7:56Drupal Commerce test
- 8:22Latency test
- 8:50CPU utilization test
- 9:12Overall results
- 9:23Muse
- 10:11Results
- 12:18Questions
related talks
26mHow MySQL Configuration Tuning Boosts App Performance
53mMySQL DevOps
43mOptimizing MySQL without SQL or touching my.cnf
53mIntroduction to MySQL Performance Tuning - workshop 1hr
57mPerformance Analysis and Optimization of MySQL
56mOptimization Techniques in MySQL
54mPerformance Analysis and Optimization of MySQL
01h 00mMySQL: a checklist for the high-load newcomer