MySQL 8.4.10Captured
See how SQL becomes a real data flow
Replay a MySQL 8.4.10 execution plan and the row sets from a deterministic fixture in one synchronized view.
Open workbench
Compare how the same SQL produces a full scan and a composite-index access path, grounded in actual rows.
Interactive labs
Compare six execution topics directly
Trace query flow, composite indexes, cardinality estimates, join algorithms, internal temporary work, and secondary-index storage against SQL, plans, and real rows.
- LAB 01 Open lab
Order Search Execution
Compare the table, index, filter, join, sort, and result flow produced by the same order query with a full scan and a composite index.
- LAB 02 Open lab
Composite Index Anatomy
Switch among three index orders and follow the equality prefix, first range, ICP, base-row lookup, and index-only projection through real plans and rows.
- LAB 03 Open lab
Cardinality & Histograms
Compare how absent, fresh, and stale histograms change filtered and estimated Filter rows over identical data, grounded in captured buckets, plans, and 128 actual rows.
- LAB 04 Open lab
Nested Loop vs Hash Join
Compare Hash Join build/probe flow with Indexed Nested Loop outer/inner lookups over identical SQL and fixture data, grounded in native plans, actual rows and loops, and exact matched pairs.
- LAB 05 Open lab
Internal Temporary Work
Trace the internal temporary rows, filesort, and LIMIT boundary produced by one GROUP BY query across RAM, mmap overflow, and InnoDB on-disk profiles, grounded in exact rows and captured memory.
- LAB 06 Open lab
Secondary Index & Buffer Pool
Trace one non-covering range query from a secondary entry and carried primary key to its clustered row, then compare captured cold and warm Buffer Pool pages and counters.
Workbench
Four synchronized surfaces
- SQL
The active clause and predicate
- Execution Plan
The active operator, access type, selected key, rows, and cost
- Data Lens
Table scans, index candidates, filters, joins, sorting, and result rows
- Plan & Evidence
The raw plan line and source behind each metric
Evidence methodology
Evidence stays separate from explanation
Every visible value is labeled by where it comes from.
- Captured
- EXPLAIN, Performance Schema, Handler counters, and results from MySQL 8.4.10
- Derived · fixture
- Exact row sets calculated by applying the same predicate to the fixed fixture
- Logical model
- A B-tree teaching model built from the index definition and candidate keys