Estimate concurrent-session capacity for a cloud gaming server by checking both compute utilization and bandwidth. Enter the server's processing budget, average processing demand per active session, total network throughput, per-session bandwidth, and desired safety headroom. The calculator identifies the binding resource and reports a conservative usable concurrency estimate. Use it for early sizing, then validate the assumptions with representative load tests.
Usable sessions = floor(min(Compute budget ÷ compute/session, Bandwidth ÷ bandwidth/session) × (1 − headroom))
The main result is a conservative per-server concurrency estimate. The lower raw capacity identifies which entered resource reaches its limit first.
Average-demand models omit bursts, protocol overhead, latency targets, failover, memory, storage I/O, and regional constraints. Confirm capacity with production-like tests.
With 100 compute units at 0.02 per session, compute supports 5,000 sessions. With 1,000 Mbps at 5 Mbps per session, bandwidth supports 200. After 20% headroom, usable capacity is floor(200 × 0.8) = 160 sessions.
It reduces usable capacity so the planned peak stays below the theoretical concurrency limit.
Yes. Enter the combined per-session traffic that constrains the selected server bandwidth limit.
Both resources are required, so the first resource to reach its limit becomes the bottleneck.
Yes. Enter total server bandwidth and per-session bandwidth in Mbps so their ratio produces a session count.
No. It is a planning estimate. Validate protocol overhead, burst behavior, latency, and real application performance with load testing.
| Input | Meaning |
|---|---|
| Compute budget | Total processing capacity in consistent units |
| Compute/session | Average active-session demand |
| Bandwidth | Available server network throughput |
| Headroom | Capacity intentionally left unused |