Back to explorer
Core Fundamentals• 25 Min

Latency & Scale Numbers Every Architect Must Know

EASY

Latency & Scale Numbers Every Architect Must Know

In system design interviews, demonstrating intuition for physical hardware bounds, I/O latencies, and network transfer speeds separates Junior developers from Staff Engineers.


1. Computer Latency Numbers (Order of Magnitude)

OperationReal TimeScaled to Human Seconds (1 CPU cycle = 1 sec)
L1 CPU Cache Reference0.5 ns1 second
L2 CPU Cache Reference7 ns14 seconds
RAM (Main Memory) Read100 ns3.3 minutes
Read 1 MB sequentially from RAM3,000 ns (3 µs)1.6 hours
Read 1 MB sequentially from NVMe SSD250,000 ns (250 µs)~3 days
Read 1 MB sequentially from Spinning HDD20,000,000 ns (20 ms)~7.5 months
Same Datacenter Round Trip (LAN)500,000 ns (0.5 ms)~6 days
Cross-Continent Round Trip (SF to NYC)40,000,000 ns (40 ms)~1.3 years
Trans-Atlantic Cable (NYC to London)100,000,000 ns (100 ms)~3.2 years

2. Capacity Sizing Rules of Thumb

  • Seconds in a Day: $\approx 86,400 \approx 10^5\text{ seconds}$.
  • QPS Rule: 1 Million requests per day $\approx 12\text{ QPS}$.
  • 100 Million requests per day: $\approx 1,200\text{ QPS}$.
  • 1 Billion requests per day: $\approx 12,000\text{ QPS}$.
  • Single Redis Instance Max Throughput: 100,000 QPS (single-threaded CPU bound).
  • Single PostgreSQL Primary Instance: 5,000–10,000 read QPS, 1,000–2,000 write QPS before sharding.
  • Single Kafka Broker Partition: 10–20 MB/sec sequential throughput.