Server Capacity Calculator
How many servers a given request rate needs — from peak traffic, how long each request takes and how much headroom you keep — including the spares to survive a failure.
A server that handles a request in 200 ms can serve at most 5 requests per second per worker thread.
How the server capacity calculator works
A server that handles a request in 200 ms can serve at most 5 requests per second per worker thread. Multiply by the number of workers, apply a utilization target well below 100% (queues grow explosively as a server approaches saturation), and divide the peak rate by the result. The N+1 figure adds enough capacity to lose a server and still serve the peak — without it, a failure at the busiest moment cascades.
Formula: capacity per server = workers ÷ response time × utilisation; servers = peak rate ÷ capacity
Worked examples
| Inputs | Servers needed | Note |
|---|---|---|
| 500 req/s, 200 ms, 16 workers | 9 | 56 req/s per server → 9 servers |
| A fast API — 50 ms responses | 5 | 448 req/s per server → 5 servers |
| A slow reporting endpoint | 13 | only 1.6 req/s per server → 13 servers |
FAQFrequently asked questions
Why not run servers at 100% utilization?
Because queueing delay rises steeply as utilization approaches saturation. At 70% a burst is absorbed; at 95% the same burst becomes a timeout.
What is N+1?
Enough servers to carry the peak with one machine lost. Without it, a failure at the busiest moment cascades into an outage.
How do I find my peak rate?
Look at the busiest minute of the busiest day, not the daily average. Traffic is rarely even.
What counts as a worker?
Whatever limits concurrency on your server — threads, processes, or a connection-pool size. It is usually smaller than you think.
Does this apply to autoscaling?
Yes — it tells you the steady-state count. Set minimums from this and let the scaler handle bursts, remembering that new instances take time to warm up.
Where these figures come from
- IEC 80000-13 — Information science and technology (quantities and units) — the decimal (kB, MB) versus binary (KiB, MiB) prefixes used throughout
- RFC 4632 — Classless Inter-domain Routing (CIDR) — the address-plan arithmetic behind the subnet calculator
- RFC 1918 — Address Allocation for Private Internets — the private ranges the subnet calculator recognises
- NIST SP 800-63B — Digital Identity Guidelines, Authentication — length over composition rules; the basis of the password guidance here
- NIST SP 800-57 Part 1 — Recommendation for Key Management — key-strength comparisons used by the key-space calculator
- NIST — Digital Identity Guidelines (SP 800-63) — US federal authentication standard
Last checked: September 2026. Units follow the SI decimal convention (IEC 80000-13 defines the binary alternatives); network and security figures cite the defining standard.