Dedicated CPU plans that still lose CPU time
Dedicated-CPU plans ranked by their worst minute of CPU steal. Dedicated should mean zero, which means you don't want to end up on this list.
| # | Plan | Median worst minute | Worst minute seen | Runs with a 5% minute | Runs | Dates |
|---|---|---|---|---|---|---|
| 1 | Linode Dedicated 8GB | 0.32% | 0.98% | 0 of 3 | 3 runs, 3 locations | Oct 7 to Oct 12 |
| 2 | RamNode 8GB VDS | 0.27% | 0.47% | 0 of 3 | 3 runs, 3 locations | Oct 11 to Oct 12 |
| 3 | DigitalOcean CPU-Optimized 2 vCPU / 4 GB | 0.18% | 5.0% | 1 of 3 | 3 runs, 3 locations | Oct 5 to Oct 8 |
| 4 | Linode Dedicated 4GB | 0.08% | 0.12% | 0 of 4 | 4 runs, 4 locations | Oct 6 to Oct 9 |
| 5 | Linode Premium 4GB | 0.05% | 0.05% | 0 of 3 | 3 runs, 3 locations | Oct 5 to Oct 12 |
| 6 | OVHcloud C3-4 | 0.03% | 0.04% | 0 of 3 | 3 runs, 3 locations | Oct 5 to Oct 12 |
| 7 | Vultr CPU Optimized AMD 1 vCPU / 2 GB | 0.03% | 0.07% | 0 of 3 | 3 runs, 3 locations | Oct 11 to Oct 12 |
Left out because the host never reported any steal, which usually means it isn't exposed to the server rather than that none happened: Hetzner CCX13.
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.
- Steal is measured once a second for the whole run, counting only the seconds where the server was asking for at least half its CPU. Steal on an idle server doesn't tell you much.
- A run only counts if it has at least 5 minutes of that kind of load.
- The worst minute is the worst 60-second average in a run. Single-second spikes are mostly noise, so they aren't used.
- A plan is marked stolen when at least 2 of its runs had a minute with 5% steal or more.