Skip to content
Learn/

Capacity Estimation

1 / 4

Why estimate at all

Estimation is not about being right. It is about being right to within an order of magnitude, quickly, so you can rule out whole categories of design before spending a week on one.

"Ten million users" tells you nothing on its own. Ten million users generating 100 GB a day and ten million generating 100 TB a day are completely different systems — one fits on a laptop and one needs a distributed store. Five minutes of arithmetic separates them.

The habit to build: convert every requirement into requests per second, bytes per day, and bytes at rest. Those three numbers determine most of your architecture.

Useful conversions

1 day        ≈ 86,400 s   ≈ 10⁵ s
1 month      ≈ 2.5M s
1M req/day   ≈ 12 req/s
1B req/month ≈ 400 req/s

Peak is usually 2–5× the average.
Size for peak; pay for average.

3 components2 connections0:00

Traffic
4Kreq/s
p50
45ms
p99
101ms
Errors
0.06%
Dropped
2.4req/s
Cost
$534/mo