Hot vs warm vs cold storage: how to tier your data for cost and performance
Not all data needs the same storage performance. Tiering puts frequently accessed data on fast, expensive media (NVMe SSDs) and rarely accessed data on slow, cheap media (HDDs, tape, cloud archival). Getting this right saves money without sacrificing performance. Getting it wrong means either overspending on flash you don't need or making users wait for data that should be hot.
How this is calculated
Hot tier: NVMe SSD, data accessed multiple times per day. Database primary storage, active project files, container images. Warm tier: HDD or S3 Standard, data accessed weekly to monthly. Older logs, completed project archives, backup sets less than 30 days old. Cold tier: S3 Glacier or LTO tape, data accessed yearly or less. Compliance archives, raw data from completed research projects, backups older than 90 days. The latency difference between hot and cold can be 100,000x (100 µs vs 10+ seconds for retrieval from deep archive). Cloud providers automate tiering with lifecycle policies. On-premises, tools like automatic storage tiering in ZFS and Storage Spaces do the same.
Verdict
Tier your storage. Keep hot data on NVMe, warm data on HDD or cheap object storage, and cold data in archival. The cost difference between NVMe and archival is roughly 50-100x per GB. For a 100 TB dataset, correct tiering can save thousands per month.
More Latency scenarios
Frequently asked questions
How much faster is L1 cache than RAM?
Is NVMe SSD faster than RAM?
Why is HDD so much slower than SSD?
What's the point of L3 cache?
How many nanoseconds is one CPU cycle?
Does DDR5 have lower latency than DDR4?
Related tools
RAM Latency Calculator
Convert DDR3/DDR4/DDR5 timings (CL, tRCD, tRP, tRAS) into true latency in nanoseconds.
Use tool ➜RAID Calculator
Calculate usable capacity and fault tolerance for RAID 0, 1, 5, 6, and 10.
Use tool ➜Display Bandwidth Calculator
Check if your HDMI/DP cable supports your resolution and refresh rate.
Use tool ➜