Capacity planning: turn users into requests, storage, and bandwidth
Capacity Planning
2 of 5
Requests Per Second
Every other number flows from this one. Get it wrong and everything else is wrong.
RPS is the single most important number in system design. It tells you how many servers to buy, how large to size your DB, and how much bandwidth to provision. It all starts here.
Formula
RPS = (DAU Γ actions/day) Γ· 86,400
This gives average RPS. Multiply by 3β5Γ for peak traffic (evenings, events, launches).
Only a fraction of registered users open the app each day
Every action is at least one API call
This is the total daily request volume
Traffic is NOT spread evenly β this is just the average
Plan for THIS number β average capacity collapses at peak
Plus 30% headroom = provision 17 servers minimum
Takeaway: 13 servers for 500M registered users. Not 500. Not 5,000. The math matters β over-provisioning by 10Γ costs a million dollars/year in wasted compute.
