§ Operations · What-If Analysis
Traffic Spike Simulator
Model hypothetical traffic spikes and observe how mesh capacity responds. Analyze latency impact and cost implications.
Simulation Parameters
+50%
From 5,000 to 7,500 req/hr
2h
+1h
Approximate time: 1:43:11 AM
5.0k/hr
📊 Scenario Summary:
• Sudden spike in 2 hours
• Peak: 7,500 req/hr
• Starting: 1:43:11 AM
Capacity Status
Under spike scenario
Capacity Used
176%
Peak Requests
7.5k/hr
⚠️ Capacity bottleneck detected. Cloud routing will increase significantly.
Latency Impact
Baseline150ms
Under Spike300ms
+150ms increase
Mesh Capacity
Healthy Nodes85
Total Capacity4.3k req/hr
Per Node50 req/hr
Routing Distribution (Under Spike)
Local28%
Mesh17%
Cloud55%
💡 Recommendation
Scale cloud capacity or reduce local load
Cost Impact
During spike period
Additional Cost
$-0
Cost Increase
+0%
Normal Period Cost
Hourly (baseline)$0.04
Daily$1
Monthly$30
During Spike
Hourly (spiked)$NaN
Duration hours
Spike Cost$-0
Cost by Route (During Spike)
Local (no cost)$0
Mesh cost$0
Cloud cost$1
Cost Optimization Insight
If you scale the mesh by just 65 additional nodes, spike cost would reduce by ~0%.
Share Results
Findings
Add Annotation
Action Items
No action items yet
Capacity Timeline
- Mesh Capacity
- Traffic
Capacity Utilization %
Peak Traffic
7.5k
req/hr
Peak Utilization
176%
of capacity
Margin
-76%
available
💡 Simulation Guide: Define a traffic spike scenario to understand how the current mesh would respond. Observe capacity utilization, latency impact, and additional costs. Use this to plan for scaling or traffic management strategies.