Capacity estimation translates user activity into the rates and volumes a design must support. A user count becomes useful only after you specify what those users do, how much data each operation moves and the interval over which the activity occurs. Those assumptions connect a product requirement to a server, storage or network limit.
Suppose one million daily active users each read 20 posts and publish two posts. Assuming one request per action, the service receives 22 million requests per day, about 255 per second on average. If a stated peak factor is five, peak demand becomes about 1,273 requests per second. Neither the request rate nor the peak factor follows from the user count alone.
Cancel the units before rounding the answer
Dimensional analysis checks a calculation by following its units. Users multiplied by requests per user per day gives requests per day. Dividing by 86,400 seconds per day gives requests per second, often called QPS. Keeping units beside intermediate values catches a missing day-to-second conversion before it becomes a machine count.
Change one assumption at a time
Which results does each assumption move? Double the reads per user, then the writes, then the retention period and the number of copies, and compare peak QPS, bandwidth and stored bytes.
Increasing peak traffic changes the serving requirement without changing the day’s stored volume. Increasing retention changes stored volume without changing incoming QPS. Those separate effects tell you whether to investigate serving capacity, bandwidth or storage.