Overview
Servers are sized by requests per second, while business numbers are usually users per day. This converter bridges the two.
Enter daily users, requests per user and a peak multiplier.
Worked examples
| Inputs | Result |
|---|---|
| Daily active users500,000Requests per user per day40Peak multiplier3 | Average: 231.5 requests per secondPeak: 694.4 requests per secondTotal: 20,000,000 per day600,000,000 per month |
Show 2 more examples
| Daily active users10,000Requests per user per day100Peak multiplier5 | Average: 11.6 requests per secondPeak: 57.9 requests per secondTotal: 1,000,000 per day30,000,000 per month |
| Daily active users5,000,000Requests per user per day20Peak multiplier2 | Average: 1,157.4 requests per secondPeak: 2,314.8 requests per secondTotal: 100,000,000 per day3,000,000,000 per month |
Average by daily active users
With the calculator's starting values, the average is 231.5 requests per second. The table shows how it changes with the daily active users.
| Daily active users | Average (requests) |
|---|---|
| 300,000 | 138.9 requests per second |
| 400,000 | 185.2 requests per second |
| 500,000starting value | 231.5 requests per second |
| 600,000 | 277.8 requests per second |
| 700,000 | 324.1 requests per second |
Other inputs: Requests per user per day: 40 · Peak multiplier: 3. Change them in the calculator above for your own numbers.
How it works
Average RPS = users × requests per user ÷ 86,400. Multiply by the peak factor for sizing.
The formula
| 86,400 | Seconds in a day |
Practical tips
- 500,000 users with 40 requests each average 231.5 RPS, and about 694 at a 3× peak.
- Traffic is rarely spread evenly across the day.
- Load test to at least your expected peak.
Frequently asked questions
What peak multiplier should I use?
Commonly 2–5×, more for events or launches.
Does caching change this?
It reduces load on your origin but not the number of client requests.