The dedicated-versus-VPS question for CS 1.6 comes down to one word: steal. A VPS shares physical cores with other tenants through a hypervisor, so under contention your single-threaded server can be denied the CPU it needs. A dedicated server has no hypervisor and no neighbours, so it never loses a cycle to anyone. Everything else — price, flexibility, management — flows from that one architectural difference. Here is how to decide which you actually need.
1. The core difference
| VPS | Dedicated | |
|---|---|---|
| CPU cores | Shared vCPUs, scheduled by the host | Full physical cores, all yours |
| Steal time | Possible, worse on oversold nodes | None, ever |
| FPS consistency | Varies with neighbours | Rock-steady |
| Price | Cheap, pay per slice | Higher, whole machine |
| Flexibility | Resize/redeploy in minutes | Fixed hardware, slower to change |
2. Why steal is the whole story
CS 1.6 is single-threaded per server, so it needs one core to be available the instant a frame is due. On a VPS, when a neighbour spikes, the hypervisor may hand your core away for a slice of time — that is steal, and it shows as evening lag that tracks the clock rather than your player count. A dedicated box has no one to steal for, so its server FPS holds flat at peak. For a competitive server where hit registration must be consistent, that consistency is the product.
3. When a VPS is the right call
A VPS is not a compromise for most servers — it is the sensible default when:
- You run a public / casual server where a few ms of jitter at peak is invisible to players.
- You want to start small and cheap and scale later.
- You value being able to resize or redeploy in minutes.
- You pick a host with low steal — a good VPS on a non-oversold node performs indistinguishably from bare metal for one or two servers.
The failure mode is not "VPS" — it is a cheap oversold VPS. A quality VPS with a fast core and near-zero steal runs a smooth server.
4. When dedicated earns its cost
Go dedicated when:
- You run a competitive / match server where consistent tick and hit-reg are non-negotiable.
- You host many servers and want guaranteed cores per instance without fighting neighbours — see packing many servers, which is far more predictable on owned cores.
- You have measured persistent steal on VPS plans and no host will fix it.
- You want to set the
performancegovernor and pin cores — things you fully control only on bare metal.
5. The middle ground: dedicated-vCPU VPS
Many providers now sell a tier variously called "dedicated CPU" or "CPU-optimized" — a VPS whose vCPUs map to reserved physical cores that are not shared. This gives you near-dedicated steal behaviour (effectively zero by design) at a price between a shared VPS and a whole machine, while keeping VPS flexibility. For a competitive single server it is often the sweet spot: you get the consistency that matters without paying for a full box you will not fill. Confirm the plan genuinely pins cores — ask, and then measure steal to verify.
6. Control you gain on bare metal
Beyond steal, a dedicated machine hands you low-level tuning that a VPS simply does not expose. You can set the CPU frequency governor, disable deep idle C-states, place NIC interrupts on a dedicated core, and pin each server to its own core — all of which shave jitter off a high-FPS server. On a typical VPS, scaling_governor may not even exist because the host owns frequency policy, so those levers are off the table. For most public servers this control is not worth the price difference; for a lag-sensitive competitive server it is part of what you are paying for. Weigh it honestly: if you would never touch a governor or an IRQ affinity mask, you are not buying anything the extra money on bare metal unlocks, and a good low-steal VPS is the smarter spend.
Common mistakes
- Assuming VPS = bad — a good VPS with low steal is fine for most servers. The enemy is oversubscription, not virtualization.
- Paying for dedicated you don't need — a casual public server does not benefit enough to justify a whole machine. Match the tier to the need.
- Buying a shared VPS for a competitive server — peak-hour steal will bite exactly when the match matters. Use dedicated or a dedicated-vCPU plan.
- Not measuring — decide with
%stfrom a trial, not with the label on the plan.
Verification
Whichever you choose, prove it before you commit the community to it. On a trial VPS, run vmstat 1 and top through an evening peak and read the st column — near zero means the shared plan is good enough; sustained double digits means you need dedicated or a dedicated-vCPU tier. On a dedicated box, confirm steal is a flat 0.0 (it will be) and that your server FPS holds steady at peak population. The decision is not ideological — it is whatever keeps %st at zero and FPS flat for the money you want to spend.
