db-performance-inspector

To diagnose slow MySQL queries, analyze the EXPLAIN execution plan to evaluate index effectiveness and cardinality, revealing bottlenecks where schema structures lack proper data distribution optimization.

Analyzing database indexing and cardinality involves inspecting schema structures and data distributions to evaluate index effectiveness, ensuring that MySQL statistics support optimal query performance for production workloads.

Generate migration-ready code by identifying schema inefficiencies and slow queries, then proposing concrete index additions and schema optimizations as implementation code to resolve database performance issues.

Yes, this approach targets MySQL databases in production workloads, directly analyzing current index usage, data distributions, and slow queries to propose schema optimizations without disrupting existing structures.

High cardinality indexes underperform in MySQL when schema structures and data distributions are misaligned, making index effectiveness poor despite high cardinality, requiring execution plan verification to diagnose.

You should not add indexes to optimize slow queries when existing index usage is already effective, as unnecessary indexing increases write overhead and storage without improving MySQL query performance.