NVMe SSD

An NVMe SSD is a solid-state drive that communicates over PCIe using the NVMe protocol, not SATA or AHCI. The result is lower latency, deeper queues, and much higher IOPS than a SATA SSD. In hosting, this shows up in databases, sessions, and applications that read many small files.

How it differs from SATA

A SATA SSD uses one queue with 32 commands. NVMe uses many queues and thousands of commands. SATA throughput is usually around 500 to 600 MB per second, while NVMe can reach thousands of MB per second depending on the PCIe lanes.

Brochure numbers are peak sequential. Hosting load is usually small random reads and writes, so IOPS and latency matter more than large throughput.

Measure it

sudo fio --name=randread --ioengine=libaio --iodepth=32 \
  --rw=randread --bs=4k --direct=1 --size=1G --numjobs=4 --runtime=60
ioping -c 20 /var/lib/mysql

fio tests a synthetic load. ioping shows directory latency. Test on a volume not used by production and compare before and after migration. For databases, also check iostat -x 1 and I/O wait.

What you notice

Database queries that waited on disk can become much faster. PHP sessions and file cache respond faster. Deploys and archive extraction finish sooner. Backups can be faster too, but are still limited by network and CPU.

NVMe does not help when the bottleneck is CPU, an unindexed query, or database connections. See vCPU, MySQL Indexing, and Connection Pooling.

Pitfalls

Capacity and DRAM matter. Cheap DRAM-less SSDs can slow down under heavy writes. High-write workloads also have a finite lifespan, so monitor SMART and TBW.

Make sure the filesystem and virtualization support TRIM. On a VPS, NVMe is often shared, so a busy neighbor can still affect latency. An M.2 slot may also share PCIe lanes with a GPU or another slot.

Backups are still required. NVMe is fast, not redundant. Use RAID and offsite backups.

Recommendation

For a production database, choose NVMe with enough capacity, DRAM cache, and SMART monitoring. Do not fill the disk almost full. For a small app, more RAM or query optimization may be cheaper than paying a premium for NVMe.

NVMe is often paired with block storage. If the server runs many containers, also consider I/O limits and Docker.

FAQ