Shared VPS plans with the worst CPU steal spikes
Shared-CPU plans whose worst minute of CPU steal hits 6.65% or more, taken as the median across runs so one bad host can't carry a plan.
| # | Plan | Median worst minute | Worst minute seen | Median steal | Runs | Dates |
|---|---|---|---|---|---|---|
| 1 | RamNode 2GB Standard | 36.3% | 66.1% | 27.1% | 4 runs, 3 locations | Oct 20 to Oct 27 |
| 2 | Scaleway DEV1-S | 21.2% | 34.4% | 7.4% | 4 runs, 4 locations | Oct 21 to Oct 25 |
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 CPX02.
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.
- 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 listed when its median worst minute is 6.65% or more, 33% past a 5% minute.