Relate request worker capacity to an explicit request rate per active user.
A worker is assumed occupied for the whole entered request time. The model excludes queueing, idle browser connections, database bottlenecks, burstiness and network limits. Do not interpret the result as a concurrent TCP connection limit.
01 / INPUT
Your calculation
Enter your values below.
YOUR RESULT · Calculating…
Ready when you are.
Enter your values and select Calculate.
Calculated with unrounded values. Display precision follows each result.
Planning estimate only. Measure your actual workload and validate changes under realistic load before applying a server configuration.
Check the working.
Read the formula and worked example below to understand your result.
A worker is assumed occupied for the whole entered request time. The model excludes queueing, idle browser connections, database bottlenecks, burstiness and network limits. Do not interpret the result as a concurrent TCP connection limit.
The formula
Ideal requests/s = workers / request time in seconds. Active users = floor(requests/s / requests/s/user).
A quick example
Twenty workers occupied for 200 ms each imply 100 requests/s. At 0.2 requests/s per active user, the simplified capacity is 500 active users.
How to use this calculator
Choose the settings that match your scenario, using the units shown beside each field.
Enter average requests per second per active user, average occupied worker time per request (ms), available request workers.
Calculate, then review the method and assumptions alongside the results.
A few common questions
Why must requests per user include a time unit?+
A capacity calculation needs a rate. Five requests per minute per user is 5/60, or about 0.0833 requests per second.
Does a larger worker pool always increase capacity?+
No. CPU, database contention and memory pressure can reduce throughput when concurrency is too high.