Live query triage
Identify the statements and sessions consuming CPU at the moment of saturation, ranked by real cost.
Emergency fix plan
We trace the queries and parameters driving CPU saturation and bring the instance back under the safety line — usually within one engagement day.
Diagnosis context
CPU saturation is a symptom with several possible sources: a newly introduced query plan, a parameter change, cache misses that turn CPU into the only escape valve, or a workload that quietly outgrew its instance. We separate these signals on the live system using processlist sampling, performance_schema digest analysis, and OS-level profiling — no guesswork, no blind restarts.
What the fix plan covers
Identify the statements and sessions consuming CPU at the moment of saturation, ranked by real cost.
Undo buffer-pool and cache misconfigurations that push work into the CPU instead of memory.
Add or adjust indexes so the worst statements stop rescanning large tables per request.
A written account of the cause, the fix, and the monitoring that prevents recurrence.
Execution path
Capture live signals: processlist, digests, OS metrics
Isolate the dominant CPU consumers and their plans
Apply parameter and index corrections on staging
Roll into production with rollback ready
Verify CPU curve against the pre-incident baseline
Measured outcome
A database that runs below its CPU safety line again — with the root cause documented, not just the symptom suppressed.
Common Questions
Emergency engagements start with a live diagnostic session — processlist sampling, digest analysis, and parameter review. Stabilization typically lands within one engagement day, with the root cause documented and a monitoring hook to catch recurrence.
Yes, when the strategy matches the change. Instant DDL covers many column operations in MySQL 8; in-place operations fit others; and gh-ost or pt-online-schema-change handle the rest with throttling tied to replica lag. We classify every change before anyone runs it, then rehearse on a production-size replica.
It is an ordering problem, and the fix usually spans both sides. We map the lock graph and specify the transaction re-sequencing your team applies — typically a small, single-commit change. Isolation levels and index design, which are database-side, do most of the heavy lifting.
Because queries filtering or sorting on JSON paths scan without an index. The fix keeps your flexible schema: virtual generated columns over the hot paths, indexes on those columns, and predicate rewrites at the database layer. Your application continues reading the same JSON.
Work with Burj
Tell us what is slow — CPU, queries, migrations, or cost — and we will scope the smallest safe fix.