---
title: "Dedicated Server vs VPS for CS 1.6 Performance"
excerpt: "The real performance difference between a dedicated server and a VPS for CS 1.6, when shared hosting is fine, and when steal-free dedicated hardware is worth the cost."
category: "optimization"
tags: "vps, hardware"
image: ""
read_time: "8 min read"
---
<p>The dedicated-versus-VPS question for CS 1.6 comes down to one word: <strong>steal</strong>. 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.</p><h2>1. The core difference</h2><table><thead><tr><th></th><th>VPS</th><th>Dedicated</th></tr></thead><tbody><tr><td>CPU cores</td><td>Shared vCPUs, scheduled by the host</td><td>Full physical cores, all yours</td></tr><tr><td>Steal time</td><td>Possible, worse on oversold nodes</td><td>None, ever</td></tr><tr><td>FPS consistency</td><td>Varies with neighbours</td><td>Rock-steady</td></tr><tr><td>Price</td><td>Cheap, pay per slice</td><td>Higher, whole machine</td></tr><tr><td>Flexibility</td><td>Resize/redeploy in minutes</td><td>Fixed hardware, slower to change</td></tr></tbody></table><h2>2. Why steal is the whole story</h2><p>CS 1.6 is <a href="/tutorials/is-hlds-single-threaded">single-threaded per server</a>, 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 <a href="/tutorials/cpu-steal-time-vps">steal</a>, 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 <a href="/tutorials/measure-server-fps">server FPS</a> holds flat at peak. For a competitive server where hit registration must be consistent, that consistency is the product.</p><h2>3. When a VPS is the right call</h2><p>A VPS is not a compromise for most servers — it is the sensible default when:</p><ul><li>You run a <strong>public / casual</strong> server where a few ms of jitter at peak is invisible to players.</li><li>You want to <strong>start small and cheap</strong> and scale later.</li><li>You value being able to <strong>resize or redeploy</strong> in minutes.</li><li>You pick a host with <strong>low steal</strong> — a good VPS on a non-oversold node performs indistinguishably from bare metal for one or two servers.</li></ul><p>The failure mode is not "VPS" — it is a <a href="/tutorials/cheap-hosting-vs-real-vps">cheap oversold VPS</a>. A quality VPS with a fast core and near-zero steal runs a smooth server.</p><h2>4. When dedicated earns its cost</h2><p>Go dedicated when:</p><ul><li>You run a <strong>competitive / match</strong> server where consistent tick and hit-reg are non-negotiable.</li><li>You host <strong>many servers</strong> and want guaranteed cores per instance without fighting neighbours — see <a href="/tutorials/multiple-cs16-servers-one-vps">packing many servers</a>, which is far more predictable on owned cores.</li><li>You have measured <strong>persistent steal</strong> on VPS plans and no host will fix it.</li><li>You want to set the <a href="/tutorials/cpu-governor-performance"><code>performance</code> governor</a> and <a href="/tutorials/cpu-affinity-taskset-hlds">pin cores</a> — things you fully control only on bare metal.</li></ul><h2>5. The middle ground: dedicated-vCPU VPS</h2><p>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.</p><h2>6. Control you gain on bare metal</h2><p>Beyond steal, a dedicated machine hands you low-level tuning that a VPS simply does not expose. You can set the <a href="/tutorials/cpu-governor-performance">CPU frequency governor</a>, disable deep idle C-states, place NIC interrupts on a dedicated core, and <a href="/tutorials/cpu-affinity-taskset-hlds">pin each server to its own core</a> — all of which shave jitter off a high-FPS server. On a typical VPS, <code>scaling_governor</code> 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 <a href="/tutorials/cheap-hosting-vs-real-vps">low-steal VPS</a> is the smarter spend.</p><h2>Common mistakes</h2><ul><li><strong>Assuming VPS = bad</strong> — a good VPS with low steal is fine for most servers. The enemy is oversubscription, not virtualization.</li><li><strong>Paying for dedicated you don't need</strong> — a casual public server does not benefit enough to justify a whole machine. Match the tier to the need.</li><li><strong>Buying a shared VPS for a competitive server</strong> — peak-hour steal will bite exactly when the match matters. Use dedicated or a dedicated-vCPU plan.</li><li><strong>Not measuring</strong> — decide with <code>%st</code> from a trial, not with the label on the plan.</li></ul><h2>Verification</h2><p>Whichever you choose, prove it before you commit the community to it. On a trial VPS, run <code>vmstat 1</code> and <code>top</code> through an evening peak and read the <code>st</code> 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 <code>0.0</code> (it will be) and that your <a href="/tutorials/measure-server-fps">server FPS</a> holds steady at peak population. The decision is not ideological — it is whatever keeps <code>%st</code> at zero and FPS flat for the money you want to spend.</p>
