Use this calculator to translate projected demand and headroom into whole capacity units. It combines operational inputs with explicit planning assumptions and returns a main estimate plus supporting metrics. Use consistent time periods and cost boundaries when comparing scenarios; the output is a planning aid rather than a vendor quote or performance guarantee.
The main result summarizes the selected scenario. Supporting metrics show the cost, utilization, savings, or capacity mechanics behind it so you can identify which assumption has the greatest effect.
Cloud pricing, discounts, workload mix, service limits, and allocation policies vary. Validate inputs against your contracts, billing exports, and telemetry before making a commitment.
The default scenario grows 45,000 requests per second by 25%, adds 20% headroom, divides by per-unit capacity, and rounds up because partial nodes cannot satisfy the plan.
Include costs inside the boundary you want to manage consistently, such as usage charges, platform fees, and directly attributable shared costs.
Use a period long enough to represent normal operations, and use the same period for every input so units remain comparable.
Yes. The result is a planning estimate; replace assumptions with observed billing and usage data when it becomes available.
Calculate each scenario with the same scope and period, then compare the main result and supporting cost or capacity metrics.
No. Demand, pricing, commitments, architecture, and allocation rules can change, so review the estimate regularly.
| Input concept | How to use it |
|---|---|
| Measurement boundary | Include the same services, teams, and time period in every comparison. |
| Usage or demand | Use observed workload data or a documented planning assumption. |
| Cost or capacity | Enter the effective value for the same scope, not an unrelated list price. |