📈
🧪 Simulate
LV2 · Toolooo Standard
Explore → See → Understand → ActUnderstand it. Feature Level describes the depth of the tool experience.

Capacity Cliff Simulator

Find when growing demand crosses your safe threshold and available capacity.

EngineeringCapacityPlanningPerformanceGrowth

See the cliff before demand reaches it

Project demand, leave room for peaks, and compare a timed expansion with your current capacity. These are planning scenarios, not a forecast.

req/s
req/s
+5% / month
12 months
Peaks, expansion, temporary loss & units
1.10× average demand
80%
req/s
2 units
Month 2
Off
Month 6
1 month

Expansion adds all selected units at its planned month. Temporary loss removes that percentage of installed capacity from both plans, including added units.

Add a calendar start date to see an approximate expansion date and crossing dates alongside model months.

Demand vs capacity · Current plan

Demand and capacity over 12 monthsAverage demand and the planning peak are compared with current and expanded capacity. The dotted safe limit follows current plan. Safe-threshold result: ~Month 2.3. Full-capacity result: ~Month 6.9. Both refer to the selected horizon. Monthly values are available below.00413382561,23891,65012req/sMonths from startExpansionPlanning peak at Month 6: 958 req/s
Average demandPlanning peakCurrent capacityExpanded capacity80% safe limit · selected plan

Expansion adds 500 req/s at Month 2. No temporary loss is applied.

6
Demand · Month 6
871 req/s
Planning peak: 958 req/s
Current capacity
1,000 req/s
Peak utilization: 95.8%
Expanded capacity
1,500 req/s
Peak utilization: 63.9%

Current plan · where the limits appear

Current utilization
65.0%
Month 0 average; peak 71.5%
Safe margin now
85 req/s
Safe limit minus planning peak
80% threshold reached
~Month 2.3
Planning peak, within 12 months
Full capacity reached
~Month 6.9
100% of available capacity
Worst peak utilization
128.4%
Includes the loss window
Largest capacity deficit
284 req/s
Planning peak minus available capacity
What happened
Current plan reaches the safe threshold around Month 2.3; full capacity is reached around Month 6.9.
Why
Demand changes by 5% each month, compounded from 650 req/s. The 1.1× planning peak is compared with 80% and 100% of available capacity. The safe threshold leaves a reserve before the full-capacity limit.
Try
Try adding capacity, moving its arrival earlier, or reducing the growth or peak assumptions. Use the capacity target below to size the reserve.

Current plan vs expanded capacity

Plan80% reached100% reachedWorst peak loadLargest deficit
Current plan~Month 2.3~Month 6.9128.4%284 req/s
Expanded capacity~Month 10.6Not reached85.6%0 req/s

Crossing times use the planning peak. “Not reached” means within the selected horizon. The current plan includes temporary loss; only the expanded plan includes added units.

Capacity target

What happened
To keep the planning peak at or below 80% through Month 12, the model needs approximately 1,606 req/s of installed capacity available from the start.
Why
The target covers the largest peak-to-available-capacity ratio across the whole horizon. At 250 req/s per added unit, that means 3 additional units above your current 1,000 req/s.
Try
At the selected Month 2 arrival, the remaining horizon needs 3 added units at this block size. Check provisioning lead time before choosing that date.
Monthly values & model assumptions
Values after any change at that time. Crossings and worst cases also check the instant before each change.
MonthAverage demandPlanning peakCurrent capacityExpanded capacityCurrent peak %Expanded peak %
06507151,0001,00071.5%71.5%
16837511,0001,00075.1%75.1%
27177881,0001,50078.8%52.6%
37528281,0001,50082.8%55.2%
47908691,0001,50086.9%57.9%
58309131,0001,50091.3%60.8%
68719581,0001,50095.8%63.9%
79151,0061,0001,500100.6%67.1%
89601,0561,0001,500105.6%70.4%
91,0081,1091,0001,500110.9%73.9%
101,0591,1651,0001,500116.5%77.6%
111,1121,2231,0001,500122.3%81.5%
121,1671,2841,0001,500128.4%85.6%

Demand = starting demand × (1 + monthly growth)month. Growth is constant, including between whole months. Negative growth models a decline. A zero starting load stays zero.

The peak multiplier creates a planning envelope; it does not estimate the probability or duration of a peak. Reaching the selected safety limit means using that reserve, not predicting an outage. Reaching full capacity can create a deficit, but queueing, latency, and failure behavior are not modeled.

Expansion is instantaneous at its selected month. Temporary loss applies to the full installed capacity of both plans and restores at the end of its window. The model checks event boundaries and solves crossings within intervals; the chart samples the demand curve every quarter month.

Capacity targets are approximate. Rounded unit counts aim to keep planning peaks at or below the selected safe threshold. Include real lead times, operating overhead, and measurement uncertainty in a deployment plan.

Bounds: up to 60 months, 100 added units, −50% to +100% monthly growth, and a finite projected peak no larger than 1 quadrillion units. Optional dates use an average 30.44-day month and should be read as approximate calendar markers.

Understand Capacity Cliff Simulator

What this tool helps you understand

Plot demand growth against a current and expanded capacity plan. Explore peaks, temporary capacity loss, expansion timing, and your chosen safe-utilization threshold to see margins, crossings, and the capacity needed through the planning horizon.

When to use it

Use Capacity Cliff Simulator when engineering, capacity, and planning work raises questions about capacity planning simulator, demand growth, and utilization threshold and you need a concrete view before making the next move.

How to read the result

Compare the shape and direction of different scenarios. The useful signal is how the result changes when an input changes, rather than one isolated number.

Assumptions and limits

Demand and capacity follow the growth, peak, loss, threshold, and expansion assumptions you enter. Use the crossings as planning signals, not guaranteed forecasts.