NVMe vs SATA SSD / HDD
NVMe vs SSD vs HDD for a VPS
NVMe reaches roughly 500,000 random IOPS with sub-100-microsecond latency; a SATA SSD manages around 90,000 IOPS; a 7,200 RPM HDD manages about 150. For anything with a database, that gap is the difference between a fast application and a slow one. HDD remains rational for one thing only: bulk sequential storage priced per terabyte.
| Dimension | NVMe | SATA SSD / HDD |
|---|---|---|
| Random IOPS | ~500,000 | SSD ~90,000 / HDD ~150 |
| Latency | <0.1 ms | SSD ~0.5 ms / HDD ~10 ms |
| Sequential throughput | 3–7 GB/s | SSD ~550 MB/s / HDD ~200 MB/s |
| Cost per TB | Highest | HDD lowest by a wide margin |
| Best for | Databases, containers, boot | Archives, backups, media |
Which should you choose?
NVMe
Use NVMe for anything with a database, a container runtime or a compiler. It is the default on every line except Hold.
SATA SSD / HDD
Use HDD when you are buying terabytes and reading them sequentially — media libraries, seedboxes, backup targets.
Frequently asked questions
Does NVMe actually make a website faster?
If the site has a database, yes and noticeably. Most perceived server slowness is disk latency on queries rather than CPU.
Is HDD ever the right choice?
For bulk sequential storage, absolutely. A 4 TB HDD volume costs a fraction of the NVMe equivalent, and a seedbox or backup target does not care about random IOPS.