The interface is the difference
SATA SSDs use the same connection that was designed for hard drives. It tops out around 600 MB/s and, more importantly, handles one command queue of 32 requests. NVMe drives connect over PCIe and speak a protocol built for flash: up to 64,000 queues, each thousands of requests deep, with far less overhead per operation.
For a single large file copy the difference looks like "a few times faster". For a server juggling hundreds of small random reads, it is often an order of magnitude.
Typical numbers
| Metric | SATA SSD | NVMe SSD |
|---|---|---|
| Sequential read | ~550 MB/s | 2,000 to 7,000 MB/s |
| Random 4K read IOPS | ~90,000 | 400,000 to 1,000,000+ |
| Access latency | ~100 µs | ~20 µs |
| Command queues | 1 x 32 | Up to 64K x 64K |
These are drive-level figures. On a VPS the numbers you see depend on how storage is shared, replicated and limited, but the underlying latency advantage carries through.
Where you will notice it
- Databases. Queries that miss the cache become random reads. Lower latency per read means faster pages when the working set does not fit in memory.
- Builds and package installs. Compilers,
npm installand container image pulls write thousands of small files. - Busy WordPress and PHP sites. Session files, object caches and logging generate constant small writes.
- Backups and snapshots. Faster storage shortens the window in which a backup competes with live traffic.
Where you will not
A small static site that fits in the page cache, a VPN endpoint, or a mostly idle service will feel the same on either. If your server barely touches the disk, CPU and network latency matter more.
Replication and durability
Speed is only half of storage. A single local drive, NVMe or not, is a single point of failure. VeloxMedia stores every server's disk on SSD storage replicated across multiple nodes, so a failed drive or host does not take data offline. Replication adds a small write cost compared with one bare local drive, which is a trade we make deliberately for durability.
Measuring it yourself
fio gives a fair picture. A random-read test that resembles a database:
sudo apt install -y fio
fio --name=randread --rw=randread --bs=4k --iodepth=32 --numjobs=4 \
--size=1G --runtime=30 --time_based --direct=1 --group_reportingRun it at different times of day. Consistency across runs tells you more about a provider than a single peak result.
The bottom line
If your workload touches disk, flash storage is worth insisting on, and NVMe is the faster flavour where you can get it. Every VeloxMedia plan uses replicated SSD storage (NVMe in London), from 20 GB on Micro to 200 GB on Max, at no extra charge.