NOTE
MySQL Load Testing
Benchmarking database throughput, latency, concurrency, and saturation with realistic datasets and transactions.
This is a historical learning note and may contain outdated or incomplete understanding.
A MySQL benchmark should reproduce the relevant transaction mix, dataset/index size, connection behavior, read/write ratio, and concurrency. Report latency percentiles and errors together with throughput.
Monitor CPU, I/O latency, buffer-pool behavior, lock waits, redo/checkpoint pressure, connections, and replication impact. Synthetic QPS is useful only when the workload and hardware/configuration are documented.