MySQL Performance Schema
summary
MySQL Performance Schema monitors low‑level server behavior by collecting runtime stats into non‑persistent hardcoded tables and an internal buffer, introduced in 5.5 and extended in 5.6 and 5.7. It exposes 93 instruments across about 87 tables that track IO, mutexes, statements, stages and transactions with nesting event IDs to trace a mutex back to the originating transaction. Config is available at build, startup and runtime (but buffer sizes are fixed at init). Typical overhead is ~5% with defaults; 5.7 adds transaction, metadata and memory instrumentation, digest sizing and replication tables.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:16Why Performance Schema?
- 7:09Instruments contd...
- 8:43What does Performance Schema provide...
- 11:47Use case 1
- 14:30Use case 3
- 15:56Event Hierarchy
- 18:46Configuration
- 20:26Performance Schema Benefits & Restriction
related talks
29mMySQL Performance Schema : A great insight of running MySQL server
43mUsing MySQL Performance Schema to debug performance issues
19mMariaDB Observability
57mMariaDB 10.5 Tutorial - New Features for Troubleshooting
50mDiagnosing Database Issues With MySQL 8.0’s Performance Schema
27mMySQL 8 Observability
53mIntroduction to MySQL Performance Tuning - workshop 1hr
49mMySQL monitoring and debugging: maximum insight with minimal cost