NVMe (Non-Volatile Memory Express) is a fast storage standard for flash drives, quicker than older SATA SSDs.
NVMe is the way modern flash storage talks to a computer. Older SSDs connect through SATA, an interface designed in the era of spinning hard drives. NVMe drives connect directly to the server's PCIe lanes, the same high-speed paths used by graphics cards, and use a protocol built for flash from the start.
The practical result is that an NVMe drive can read and write data several times faster than a SATA SSD and handle far more requests at once. On a web server, that means databases and files are fetched with much less waiting.
How NVMe works
A SATA SSD sends commands through a single queue that holds 32 commands. NVMe supports up to 65,535 queues, each holding up to 65,535 commands. It also skips the older controller layer that SATA relies on, so each request has less overhead.
For a busy server handling many websites, this matters more than raw transfer speed. Hundreds of small reads and writes happen at the same moment, and NVMe can process them in parallel instead of lining them up.
NVMe vs SSD vs HDD
- HDD (hard disk drive): spinning platters and a moving read head. Cheap and large, but slow for the random reads websites need.
- SATA SSD: flash memory with no moving parts, much faster than HDD, but limited by the SATA interface.
- NVMe SSD: flash memory on PCIe, with the lowest latency and highest throughput of the three.
All NVMe drives are SSDs, but not all SSDs are NVMe. When a host says "SSD storage", it's worth checking which kind.
Why NVMe matters for your website
Most of the time spent building a dynamic page is waiting: for PHP files to load and for the MySQL database to return results. Faster storage cuts that wait, which helps your server response time and TTFB. You'll notice it most on:
- Database-heavy sites like online shops and forums
- WordPress admin pages and searches that can't be cached
- Backups, restores and imports of large files
What NVMe won't fix
Fast storage helps, but it doesn't replace good caching, optimised images or well-written plugins. A page that runs hundreds of slow queries will still be slow, just a little less so. NVMe works best as part of a stack that also includes a fast web server like LiteSpeed and an object cache.
Storage space and inodes are separate limits, too. A plan can have fast NVMe drives and still cap how many files you store.