MySQL and InnoDB Performance for the Rest of Us
summary
Practical checklist for fixing slow MySQL/InnoDB queries: use EXPLAIN and SHOW FULL PROCESSLIST to see planner choices and thread states; prefer small integer auto‑increment primary keys to avoid page splits (UUIDs cause big btree churn); understand InnoDB stores rows in a clustered primary key and secondary indexes point to that PK; design left‑most, multi‑column indexes so queries hit an covering index and avoid temp files, file sorts and excessive IO; check EXPLAIN’s type/rows/extra (rows=1 is ideal, rows≈200 indicates nested‑loop work) and use EXPLAIN EXTENDED + SHOW WARNINGS for the join plan.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:48Agenda
- 1:46Storage Engines
- 4:21Performance
- 9:11Indexes
- 12:44Clustered Indexes
- 14:19Primary Keys
- 17:35Improving Access Types
- 19:30Designing Indexes
- 22:11Index Limitations
- 22:51Covering Indexes
- 24:28Query Parser
- 27:30Post Processing
related talks
21mWriting High Performance SQL Statements
47mMySQL Indexing Best Practices
49m18 Ways to Fix MySQL Bottlenecks
53mEfficient MySQL Performance
53mIntroduction to MySQL Performance Tuning - workshop 1hr
41mMySQL Query Optimization Best Practices and Indexing
46mSupercharge Your SQL with Indexes: a Practical Introduction
36mFor performance, go to page 5: Indexes