Skip to main contentSkip to user menuSkip to navigation

One MB Transfer Times

BDP math and realistic transfer times

Not Started
Loading...

The time to transfer 1MB reveals the true hierarchy of system performance. From RAM (0.25ms) to intercontinental networks (150ms), we see a 600x difference. This impacts everything from database design (keep hot data in memory) to CDN strategy (cache large assets at the edge).

Remember: bandwidth is rarely the bottleneck—latency is. Even on gigabit networks, the round-trip time dominates small transfers. For large files, use compression (60-90% reduction for text), chunking for parallel transfers, and CDNs to minimize distance.

⚡ Quick Decision

Use RAM/SSD When:

  • • Sub-millisecond access needed
  • • Frequent data access patterns
  • • Hot data storage required

Use CDN When:

  • • Global user distribution
  • • Cross-region latency >50ms
  • • Large file downloads common

Optimize Transfer When:

  • • Mobile users with limited data
  • • Transfer times >100ms critical
  • • Bandwidth costs are significant

💡 For implementation guides and code examples: See our technology deep dives: Object Storage, Redis, NGINX

1 MB Data Transfer Times

How long it takes to move 1MB across different mediums and distances

RAM
Memory bandwidth; orders faster than disks
0.25 ms
SSD (NVMe)
Queue depth and parallelism matter
1 ms
Datacenter LAN
Depends on congestion and hops
10 ms
HDD
Seek latency dominates
20 ms
Same AWS Region
Inter‑AZ latency floor
30 ms
Cross‑Region
Regional distance and peering
80 ms
Intercontinental
Physics‑bounded RTT
150 ms
4G LTE
Radio scheduling + RTT + jitter
200 ms
LAN
relative
Cross‑region
relative
Intercontinental
relative
No quiz questions available
Quiz ID "one-mb-transfer" not found