NVMe VPS/VDS

The word NVMe has become almost mandatory in plan descriptions, but the difference between disks isn't felt in every task. To avoid overpaying — or making the opposite mistake — it helps to understand how the three types of storage differ and which numbers actually matter.

How NVMe, SATA SSD and HDD differ

• HDD — a mechanical disk. Sequential reads of 150–250 MB/s, but random access is slow: on the order of one or two hundred operations per second. Suitable for archives and backups; see HDD VPS and Storage VPS.
• SATA SSD — flash memory on an older interface. It hits the SATA bus ceiling at about 550 MB/s, but random operations already reach tens of thousands per second.
• NVMe — flash on the PCIe bus. A single drive delivers gigabytes per second and hundreds of thousands of IOPS, and most importantly, noticeably lower latency per operation and deep request queues.

On a VPS you don't get the whole disk, but your share of it: the host sets IOPS and throughput limits for each virtual machine. So "NVMe" on a plan doesn't mean 7 GB/s; it means the shared array is fast and your server has to wait for its neighbours less.

Where NVMe gives a real gain

• Databases. PostgreSQL and MySQL constantly do small random reads and write their log with fsync. What matters here is IOPS and latency, not megabytes per second. If the database doesn't fit entirely into RAM, NVMe speeds up queries several times over. More on this: VPS for PostgreSQL.
• Game servers. Minecraft, Rust and ARK write the world to disk in chunks and save it on a schedule. On a slow disk this causes lag when new areas are generated and during autosaves.
• Builds and CI. npm install, composer install, compilation and Docker layers mean thousands of small files. On NVMe the build finishes noticeably faster.
• Online stores and CMSs with a large catalogue and no full caching.

Where there's almost no difference

Your own VPN, a proxy, a Telegram bot, a static site behind nginx — all of these live in RAM and are limited by the network or the CPU. There's no need to overpay for NVMe for these tasks, although these days it often costs the same as SATA SSD. For backups and file archives capacity matters more than speed: HDD is better value there.

How to check that the disk really is fast

The label on the plan guarantees nothing: there are NVMe plans with strict limits, and SSD arrays that perform better. After the server starts, test random operations, not just linear speed:

fio --name=rand --rw=randrw --bs=4k --size=1G --iodepth=32 --direct=1 --runtime=30 --time_based

As a guideline: on a good NVMe plan, 4K random reads give tens of thousands of IOPS or more; on an overloaded SATA SSD, a few thousand. A dd test shows only sequential writes and almost always looks good, so you can't judge by it.

The table above collects plans whose disk type is listed as NVMe on the host's website. If your budget is tight, start with the selection of cheap NVMe VPS and sort by price.