Prepare a capacity note
A capacity note records observed demand, tested limits, bottlenecks and the next safe experiment. Include uncertainty rather than promising unmeasured scale.
Understand the pattern
A capacity note records observed demand, tested limits, bottlenecks and the next safe experiment. Include uncertainty rather than promising unmeasured scale.
Interpret the evidence
Report the tested 100 RPS limit for this workload and mark larger scale untested.
A tempting mistake
Promise unlimited scale from one successful load test.
All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.
Worked example and expected result
$ cat /opt/ai-lab/cases/aiops-cost-reliability-012.json{
"fixture": "Fictional training data; not a live measurement.",
"observed_rps": 80,
"tested_limit_rps": 100,
"larger_scale_tested": false
}Exit status: 0. The command completed successfully in the training fixture.
$ jq .larger_scale_tested /opt/ai-lab/cases/aiops-cost-reliability-012.jsonfalse
Exit status: 0. The command completed successfully in the training fixture.
$ printf '%s\n' 'state-tested-capacity' > /home/learner/lab/aiops-cost-reliability-012-decision.txt(no output; exit 0)
Exit status: 0. The command completed successfully in the training fixture.
Explain it
Apply it elsewhere
Keep the momentum.
Complete the lab, then explain and apply the pattern.
Next: Review cost anomaliesTry an incident drillAnonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.
Keep learning
- 01Read reliability targetsReliability targets need a measure and window. Keep user-visible success separate from process uptime so an alive but unusable system is not counted as healthy.Practice
- 02Review cost anomaliesCost anomalies require separating request volume, token length, model selection and retries. Compare those drivers before treating an invoice increase as a provider error.Practice
- 03Cost and reliability checkpointA cost/reliability decision should preserve quality, latency, privacy and bounded failure behavior. Resource savings do not justify silently breaking another contract.Practice