Access profiling
What is actually read, updated, and joined — measured across digests and logs.
Data lifecycle
Years of unpruned rows tax every query, backup, and index. We design the lifecycle that moves history out and performance back in.
Diagnosis context
Live tables grow monotonically while real access patterns age out in months. The result is predictable: larger buffer pools for cold data, slower index maintenance, longer backups, and higher bills. We profile what is actually queried, define retention per table, and implement pruning and archiving that shrinks the hot dataset without losing a record.
What the fix plan covers
What is actually read, updated, and joined — measured across digests and logs.
Per-table retention rules your compliance and product teams sign off.
Partition boundaries, batched deletes, and drop-partition strategies that never lock writes.
Cold storage or side databases wired with a documented retrieval path.
Execution path
Profile real access patterns per table
Agree retention windows with product and compliance
Implement partitioning and batched pruning
Stand up the archive tier and retrieval path
Verify backups, latency, and cost improvements
Measured outcome
Hot tables that stay hot-sized — faster queries, shorter backups, and a storage line that stops growing on autopilot.
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.