SSD vs NVMe VPS Storage: The Real Difference (and Why It Matters)

SATA SSD vs NVMe: What Actually Changes

SATA is a 20-year-old interface originally designed for spinning hard disks. It caps out at around 600 MB/s and adds real latency on every random read. SATA SSDs are much better than HDDs — but they inherit the interface’s limitations.

NVMe talks directly to the CPU over PCIe, skipping the SATA controller entirely. That means 3–7 GB/s of sequential throughput and sub-millisecond tail latency on random 4K reads. For a transactional database doing small random reads, the gap between SATA and NVMe isn’t 2× or 3× — it’s more like 10× on IOPS.

What the Numbers Mean in Practice

• Postgres / MySQL — small random reads dominate, so NVMe makes transaction latency drop visibly. A query that returned in 40ms on SATA often returns in 8–15ms on NVMe.
• Docker — image pulls and layer extraction involve a lot of small writes. NVMe cuts build pipelines noticeably, especially with multi-stage builds.
• Redis / ClickHouse persistence — persistent writes are the common bottleneck; NVMe gives you headroom to turn durability settings up without a performance cliff.
• Static sites and small APIs — honestly, you’ll barely notice. The bottleneck there is usually the network or PHP-FPM, not the disk.

How to Tell What You’re Actually Buying

Read the fine print. "SSD VPS" is marketing. "NVMe SSD" or "NVMe storage" is specific. If the landing page says just "SSD" with no qualifier, the answer is usually SATA.

Benchmark once you have the VPS. `fio --rw=randread --bs=4k --runtime=30 --name=test --numjobs=1 --size=1G --ioengine=libaio --iodepth=16 --direct=1` gives you random-read IOPS. SATA SSDs top out around 90k IOPS under load; NVMe drives on our fleet comfortably do 400k–600k. If your "SSD VPS" benches below 100k, you’re on SATA.

Ask support. "Are these NVMe or SATA drives?" is a one-sentence question — and the answer tells you whether the provider is being honest.

Why BearHost Runs NVMe Everywhere

Enterprise NVMe is now cheap enough that charging extra for it makes no sense. We run NVMe across every BearHost VPS Hosting tier — including the entry-level cheap VPS hosting plan at £3.35/mo. Same hardware, same throughput, same low latency; just a smaller allocation.

We don’t artificially throttle IOPS either. Plenty of hosts "include NVMe" but cap you at 5,000 IOPS to protect shared hardware. We run honest overprovisioning ratios and let you hit the underlying drive — the way hardware virtualization is supposed to work.

When the Storage Choice Is the Whole Decision

• If you’re running Postgres or MySQL in production — yes
• If your CI runs Docker builds — yes
• If you’re self-hosting apps like Mastodon, Nextcloud, or GitLab — yes (small random I/O dominates)
• If you’re hosting a static blog or marketing site — probably no; look at RAM and bandwidth instead
• If you’re running a game server — memory matters more than disk; NVMe helps with map loads but is rarely the bottleneck