mysql.performance.cpu_time

Sudden spike in binary log disk usage triggers CPU, network, and IOPS saturation, creating a cascading slowdown. Large write operations (bulk updates, schema changes) generate excessive binlog data faster than it can be purged, leading to storage pressure and performance degradation.

High concurrent writes waiting for InnoDB row locks reduces throughput despite available CPU/IOPS capacity. Transactions queue waiting for locks rather than executing, masking true capacity limits and increasing query latency.