NVMe plans that don't beat plain SSD
Plans sold as NVMe that land 33% or more behind the median SSD plan in the same CPU class on IOPS or throughput. They're NVMe on the spec sheet only.
The SSD median across 13 plans in this class is 55,566 4K IOPS and 1,602 MB/s with 1M blocks.
| # | Plan | Median 4K IOPS | Median 1M speed | Notes | Runs | Dates |
|---|---|---|---|---|---|---|
| 1 | CubePath gp.micro | 7,815 (14% of SSD) | 454 MB/s (28% of SSD) | Capped near 7,815 IOPS | 3 runs, 3 locations | Oct 12 to Oct 14 |
| 2 | DigitalOcean Basic AMD 1 vCPU / 1 GB | 55,427 (100% of SSD) | 481 MB/s (30% of SSD) | 4 runs, 4 locations | Oct 9 to Oct 12 | |
| 3 | OneProvider General Purpose GP1.1-1-10 | 18,908 (34% of SSD) | 1,190 MB/s (74% of SSD) | 3 runs, 3 locations | Oct 9 to Oct 12 | |
| 4 | OVHcloud D2-4 | 20,036 (36% of SSD) | 1,798 MB/s (112% of SSD) | Capped near 20,036 IOPS | 5 runs, 4 locations | Oct 6 to Oct 15 |
| 5 | UpCloud Premium 1 vCPU / 1 GB | 24,617 (44% of SSD) | 783 MB/s (49% of SSD) | Capped near 783 MB/s | 4 runs, 4 locations | Oct 6 to Oct 10 |
| 6 | OneProvider General Purpose GP1.2-4-50 | 24,949 (45% of SSD) | 3,690 MB/s (230% of SSD) | 3 runs, 3 locations | Oct 3 to Oct 12 |
How plans get on this list
- A plan needs at least 3 completed runs from the last 90 days, spread across at least 2 locations or 2 different days, so one bad host or one bad afternoon can't rank it.
- Plans are only compared with plans of the same CPU class. Shared CPU plans are never ranked against dedicated ones.
- Every completed run counts. We don't drop bad runs or rerun a plan until it looks better.
- Only plans well past the line for this board get listed, and that line is spelled out below. Plans under it still count toward the comparison, they just aren't shown.
- Disk numbers come from fio: 4K blocks for IOPS, 1M blocks for throughput, read and write combined. Runs where the CPU lost more than 10% of its time during the disk test are left out, since a starved CPU drags the disk numbers down with it.
- A plan is listed when its median, and at least 2 of its runs, land 33% or more below the median SSD plan of the same CPU class on 4K IOPS or 1M throughput. Each SSD plan counts once in that median, however many times it was tested.
- "Capped" means every run landed within 2% of the same number in different locations, which looks like a limit set by the provider rather than the drive running flat out.