Use when performing database performance tuning — provides a systematic approach to diagnosing and resolving database performance issues. Covers query analysis, index optimization, schema review, configuration tuning, connection management, and capacity planning for relational and NoSQL databases.
| Metric | Current Value | Healthy Range | Status |
|---|
| CPU utilization | % | < 70% | OK/Warning/Critical |
| Buffer cache hit ratio | % | > 99% |
| Disk IOPS | < max provisioned |
| Active connections | < max_connections * 80% |
| Avg query time | ms | < target ms |
| Deadlocks/hour | 0 |
| Query | Avg Time | Calls/min | Total Time % | Full Scans | Action |
|---|---|---|---|---|---|
| ms | % | Yes/No | Index/Rewrite/Cache |
| Table | Recommendation | Type | Affected Queries | Write Impact | Priority |
|---|---|---|---|---|---|
| Add/Remove/Modify | B-tree/Hash/GIN | Low/Med/High | 1-5 |
| Parameter | Current | Recommended | Impact | Risk |
|---|---|---|---|---|
| Low/Med/High |
| Shortcut | Counter | Why |
|---|---|---|
| "We can skip some steps for this case" | Adapt the workflow steps, don't skip them | Skipped steps are where incidents and oversights originate |
| "The user seems to already know what to do" | Complete all workflow phases with the user | The workflow catches blind spots that experience alone misses |
| "This is a minor case, full process is overkill" | Scale the process down, don't turn it off | Minor cases become major when unstructured; the process scales, not disappears |
| "I'll fill in the details later" | Complete each section before moving on | Deferred details are forgotten; real-time capture is more accurate |
| "The template output isn't necessary" | Always produce the structured output format | Structured output enables comparison, audit trails, and handoff to other teams |