High Performance MySQL

About the book

High Performance MySQL addresses the gap between getting a database to work and getting it to work well. Its territory is relational database management with MySQL specifically: query optimization, schema design, indexing, server configuration, and the operational habits that keep a busy database responsive. The authors write from hands-on administration, and the book treats performance as an engineering discipline with measurements, tradeoffs, and repeatable techniques.

The subject matter is broad by design. It covers how MySQL stores and retrieves data, how the optimizer chooses execution plans, and why a query that looks reasonable can still scan far more rows than necessary. It also reaches into replication, backups, and capacity planning, areas where a fast server can still fail under operational pressure. The emphasis falls on understanding mechanisms so that tuning decisions follow from evidence.

Because MySQL changes across versions, the book's value lies less in memorized settings than in its method: profile the workload, read the execution plan, change one variable, and measure again. That approach survives version upgrades better than any single configuration recipe.

How to read it

Approach the material with a working MySQL instance nearby. The arguments about indexes, joins, and query plans become concrete when tested against real tables and slow queries. Readers who skim the conceptual chapters without running examples will retain less, because much of the book's reasoning depends on seeing how the optimizer responds to schema and query changes.

The prose is technical and assumes comfort with SQL, server administration, and command-line tools. Expect dense passages on storage engines, locking, and replication topology. Treat the performance advice as a starting framework: verify recommendations against your own MySQL version, hardware, and workload before applying them in production. The examples illustrate principles, and they are not universal settings.

Who it suits

Database administrators, backend developers, and systems engineers who already run MySQL and need to diagnose slow queries, design better schemas, or plan for growth will find practical value here. It suits readers who prefer understanding internals over copying configuration snippets, and teams that want a shared vocabulary for performance work. Beginners should build basic SQL and administration skills first.

Reading considerations

MySQL has changed substantially since the early editions, so specific version numbers, defaults, and tooling references may be outdated. Check which edition you have and cross-reference current documentation before changing production settings. The book's performance guidance is technical, not operational policy; test any tuning change under realistic load rather than assuming a recommendation transfers directly.