Simulation Accuracy Benchmark
How close is the Cloud World Model simulation to what AWS CloudWatch would actually report? This page answers that question with a side-by-side comparison of simulated vs. reference metrics across four traffic scenarios on a canonical three-tier AWS architecture.
See also: Simulation Fidelity — benchmark data and accuracy ranges for all five cloud providers.
Reference values are drawn from AWS documentation and published load-test studies — not from live CloudWatch streams. See the Methodology section below for full source citations.
| Provider | Overall |
|---|---|
AWS | 97.4% |
GCP | 97.9% |
Azure | 97.8% |
Oracle Cloud (OCI) | 96.2% |
DigitalOcean | 97.4% |
Click any row to load that provider's full benchmark results below.
| Provider | Idle 10 req/s | Normal 100 req/s | Peak 500 req/s | Burst 1,000 req/s |
|---|---|---|---|---|
| AWS | 4.9%ref 5% | 19.1%ref 20% | 49.2%ref 52% | 74.9%ref 78% |
| GCP | 6.3%ref 6% | 22.0%ref 22% | 57.3%ref 58% | 88.1%ref 84% |
| Azure | 5.4%ref 5% | 18.5%ref 19% | 52.3%ref 54% | 86.1%ref 81% |
| Oracle Cloud (OCI) | 4.3%ref 4% | 12.1%ref 12% | 44.4%ref 48% | 82.6%ref 78% |
| DigitalOcean | 6.3%ref 6% | 15.4%ref 15% | 41.9%ref 44% | 70.3%ref 68% |
The top number is the simulator's CPU output; ref is the documentation-sourced reference. Click any row to load that provider's full benchmark below.
Select a provider to load its canonical benchmark automatically.
Overall Simulation Accuracy: 97.4%
Weighted composite across P50/P95 latency, CPU utilization, throughput, error rate, and cost — averaged over four traffic scenarios (Idle, Normal, Peak, Burst).
Idle
95%
Normal
97%
Peak
99%
Burst
98%
Results update the architecture diagram and scenario tables below.
Canonical Architecture
| Role | Instance Type | Count | Cost / hr | |
|---|---|---|---|---|
Load Balancer | ALB (Application Load Balancer) | 1 | $0.0225 | |
Web / App Server | m5.large | 2 | $0.1920 | |
Database | db.r5.large (RDS MySQL) | 1 | $0.2400 | |
| Total (official AWS pricing, us-east-1) | $0.4545/hr | |||
Want to run this exact scenario yourself? Open the Simulation Workspace and configure the same resources.
Traffic Scenario Comparisons
Each table shows Reference vs. Simulated values, the percentage delta, and an accuracy badge (green ≥ 90%, yellow ≥ 75%, red below 75%).
| Metric | Reference | Simulated | Delta | Accuracy |
|---|---|---|---|---|
| P50 Latency | 12 ms | 12 ms | +0.0% | 100% |
| P95 Latency | 28 ms | 33 ms | +17.9% | 82% |
| CPU Utilization | 5.00% % | 4.90% % | -2.0% | 98% |
| Throughput | 10 req/s | 10 req/s | +0.0% | 100% |
| Error Rate | 0.10% % | 0.10% % | +0.0% | 100% |
| Cost / Hour | $0.4545 $/hr | $0.4538 $/hr | -0.2% | 100% |
| Metric | Reference | Simulated | Delta | Accuracy |
|---|---|---|---|---|
| P50 Latency | 18 ms | 17 ms | -5.6% | 94% |
| P95 Latency | 45 ms | 44 ms | -2.2% | 98% |
| CPU Utilization | 20.00% % | 19.10% % | -4.5% | 96% |
| Throughput | 100 req/s | 100 req/s | +0.0% | 100% |
| Error Rate | 0.20% % | 0.20% % | +0.0% | 100% |
| Cost / Hour | $0.4545 $/hr | $0.4580 $/hr | +0.8% | 99% |
| Metric | Reference | Simulated | Delta | Accuracy |
|---|---|---|---|---|
| P50 Latency | 38 ms | 38 ms | +0.0% | 100% |
| P95 Latency | 90 ms | 90 ms | +0.0% | 100% |
| CPU Utilization | 52.00% % | 49.20% % | -5.4% | 95% |
| Throughput | 498 req/s | 498 req/s | +0.0% | 100% |
| Error Rate | 0.40% % | 0.40% % | +0.3% | 100% |
| Cost / Hour | $0.4545 $/hr | $0.4532 $/hr | -0.3% | 100% |
| Metric | Reference | Simulated | Delta | Accuracy |
|---|---|---|---|---|
| P50 Latency | 68 ms | 70 ms | +2.9% | 97% |
| P95 Latency | 160 ms | 159 ms | -0.6% | 99% |
| CPU Utilization | 78.00% % | 74.90% % | -4.0% | 96% |
| Throughput | 980 req/s | 980 req/s | +0.0% | 100% |
| Error Rate | 2.00% % | 2.00% % | +0.0% | 100% |
| Cost / Hour | $0.4545 $/hr | $0.4524 $/hr | -0.5% | 100% |
Pricing accuracy is validated continuously via automated drift checks in CI. See the Simulation Fidelity page for per-provider cost benchmark details across all five cloud providers.
Want to benchmark a different architecture? Open the Workspace to build and simulate any topology.
Try the Simulation Yourself
Load the same 3-tier AWS scenario in the interactive workspace and compare what you see with the reference values on this page.
