NVMe vs SSD vs HDD: Storage Choices That Actually Matter
HDDs are cheap and slow. SATA SSDs are fast enough for most things. NVMe is dramatically faster for random I/O — which is exactly what databases do. Here is when the difference is real.
By VPSoto Team · Infrastructure · October 24, 2025 · 5 min read
Storage tiers get marketed on big sequential numbers ("3,500 MB/s!"). For a server, the number that matters is random I/O — lots of small, scattered reads and writes. That is what a database does on every query.
The three tiers
- HDD (spinning disk) — cheap per terabyte, fine for cold archives, backups, and media you stream sequentially. Random I/O is dreadful: a busy database on an HDD will feel broken.
- SATA SSD — no moving parts, hugely better random I/O than HDD, capped by the SATA bus (~550 MB/s). Perfectly good for most web apps, app servers, and small-to-medium databases.
- NVMe SSD — talks to the CPU over PCIe instead of SATA. Several times the throughput and much lower latency under concurrent load. This is the one databases, busy queues, and write-heavy workloads care about.
When the difference is real
You will notice NVMe over SATA SSD when:
- You run a database under real concurrency (Postgres, MySQL, MongoDB, ClickHouse)
- You do lots of small writes — queues, logs, event streams
- You run many containers that all hit disk at once
You will not notice it for a brochure website, a low-traffic blog, or anything that mostly serves static files from RAM cache.
What VPSoto offers
Plan storage type is shown on every plan card — filter for NVMe on the VPS browser if your workload is I/O-heavy, or save money with SSD/HDD-backed plans for storage-heavy but not I/O-heavy use. Dedicated servers list their exact disk layout (e.g. 2× 1.92 TB NVMe) on each spec.
If you are not sure: pick NVMe for anything with a database, SSD for general-purpose, HDD only for bulk cold storage.
