Diagnose 100% CPU on a managed database
WHAT IT TESTS: structured DB triage. OUTLINE: correlate the spike with deploys and traffic, find top queries via the engine's views, inspect plans for missing indexes, then tune before scaling. RED FLAG: scaling up without finding the offending query.
WHAT IT TESTS: methodical root-cause analysis over reflexive scaling. ANSWER OUTLINE: first correlate the CPU spike with the timeline, deploys, and traffic; identify the top CPU-consuming queries using the engine's performance views; inspect their plans for full scans, missing indexes, or parameter-sniffing issues; check for lock contention and connection storms. Then remediate the real cause, add an index or fix the query, and scale up only if the workload genuinely needs more capacity. RED FLAG: scaling the instance before diagnosing.
Read the original → interview
- #database
- #performance
- #troubleshooting
- #rds
- #monitoring
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.