mysql> USE aditya_resume;\c aditya_resume
Aditya's resume, as a database
7 tables, 82 rows, twenty years of schema migrations. Pick a table or a saved query, then watch what the engine does underneath. Every panel switches vocabulary with the engine toggle.
Query
reads → replica
Pick a query
Choose a saved query or a table on the left. The console is guided: no typing, no SQL injection, just internals.
-- waiting for a query SHOW CREATE TABLE
result set will appear here
B+Tree index walk
—
The index descent animates here: root → internal → leaf → row.
Query plan
EXPLAIN FORMAT=TREE
Run a query to see how the optimiser executes it.
raw output
const / ref range index scan full scan
Buffer pool
InnoDB buffer pool
hit ratio100.0%
resident0 / 10
page size16 KB
Midpoint-insertion LRU hit miss (disk read) evicted
Replication topology
SHOW REPLICA STATUS
Executed_Gtid_Set
Statement digest
performance_schema…by_digest
| digest | calls | avg ms | rows examined | rows sent | access |
|---|
No statements yet. Every query you run is digested here; full scans are flagged.
MVCC: the profile row through time
undo log · read viewsxmin / xmax · snapshots
Amazon RDS instance
MySQL Community 8.4.3
DB identifieraditya_resume-prod
Classdb.r7g.2xlarge
Statusavailable
Multi-AZYes (3 readers)
Storagegp3 400 GiB · 12,000 IOPS
Parameter groupdefault.mysql8.4
CPUUtilization —%
DatabaseConnections —
ReadIOPS —/s
FreeableMemory —GB
FinOps meter · monthly run-rate −35% vs on-demand
Savings Plan coverage 87% Right-sizing r6g → r7g Fleet impact $40M+/yr
Reliability
SLO · error budget · on-call
uptime since first production shift —
availability SLO99.99%
achieved (30d)99.999%
error budget remaining 100%
on-call primaryAditya · 24/7
MTTR (sim)—
incident log
- No incidents. Try "Simulate AZ failure" in the replication panel.