Capacity planning becomes much more reliable when teams align around Requests Per Second (RPS) and latency assumptions.
Step 1: Define Target RPS by Scenario
Split RPS targets by scenario, not only by global average:
- steady-state traffic
- peak business hour
- burst campaigns
- failover/degraded mode
Step 2: Convert RPS to Concurrency
concurrency ≈ RPS * latency_seconds
This quickly reveals thread-pool pressure, DB connection pressure, and queueing risk.
Step 3: Estimate Instance Count with Safety Margin
instances_min = ceil(target_rps / per_instance_rps)
instances_recommended = ceil(instances_min * (1 + safety_margin_percent/100))
Step 4: Validate with Real Signals
After tests or production windows, validate assumptions with:
- wait-event profile
- top SQL concentration
- CPU vs I/O breakdown
The Oracle AWR Report Analyzer helps convert AWR HTML into actionable diagnostics.
Recommended Tool Flow
Using this flow gives a full loop: estimate, test, diagnose, and recalibrate.