Server Load Calculator
How many servers a request load needs — from requests per second, response time and the concurrency each server can hold.
Little's Law does the work: the concurrent requests in flight equal arrival rate times response time.
How the server load calculator works
Little's Law does the work: the concurrent requests in flight equal arrival rate times response time. Two hundred requests a second at 250 ms each means fifty in flight at any moment, and that is what the servers must hold.
As with any queue, the target utilisation matters more than the raw capacity. Sizing to 100% means response times climb without bound at the first burst.
Formula: concurrency = rate × response time (Little’s Law)
Worked examples
| Inputs | Servers needed | Note |
|---|---|---|
| 200 req/s at 250 ms | 6 | 3 servers |
| A slower endpoint | 21 | concurrency triples |
| A bigger peak | 12 | double the servers |
FAQFrequently asked questions
What is Little's Law?
Concurrency equals arrival rate times time in system. It holds for any stable queue regardless of the distribution, which is what makes it so useful.
Why does response time affect server count?
Because a slower request occupies a worker for longer. Halving response time halves the concurrency for the same request rate.
What concurrency can one server hold?
It depends on the runtime and what the work is. A thread-per-request server is limited by threads; an async one by memory and downstream capacity.
Should I size for peak or average?
Peak, with headroom. Sizing to average guarantees the site falls over at the busiest moment, which is the moment it matters.
Does autoscaling remove the need for this?
No — it changes when you pay, not how much capacity the load needs. You still need to know the numbers to set the scaling policy.
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
- Australian Cyber Security Centre — Essential Eight — national guidance on passphrases and system hardening
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.