What is overselling, and why do cheap hosts always lag?

🍕 What is overselling, and why do cheap hosts always lag?

Engine (base): dedicated resources (dedicated CPU threads).

Article type: hosting market analysis and a look at the technology.

Highlight: complex server processes explained in plain words for regular players.

Author: Servup

Sooner or later every game server admin runs into this: the player count grows, it's prime time (a weekend evening), players have great ping (15–25 ms), yet the game turns into a slideshow. Models move in jerks, Var jumps, and hits (sub-tick) simply stop registering. In 99% of cases the culprit is overselling. In this article we'll look at how hosts sell thin air and why it ruins your game.

💡 What is overselling?

A simple pizza analogy Imagine a chef who has baked just one pizza, cut into exactly 8 juicy slices. Logically, it can feed 8 people. But the chef is hungry for money, so he decides to sell tickets for this pizza to 30 different people!

He's counting on the 30 customers never coming at the same time. And indeed: one came in the morning, two at lunch, they ate their slices and left happy. But then it's Friday evening, and all 30 people walk into the pizzeria at once.

Chaos. The chef panics and tries to split the 8 slices into microscopic crumbs. In the end every customer leaves hungry, angry and empty-handed. Overselling is exactly that: selling 30 tickets for 8 slices of pizza.

🎮 How does this trick work at game hosts? A host has a powerful physical processor with, say, 12 threads. For the servers to run perfectly, it can carry at most 8–10 CS2 game servers.

What does a dishonest host do to earn more? It puts 40 or 50 servers on it! The bet is that servers are empty during the day and school kids and students sleep at night. But as soon as evening comes:

• All players join at once to play with their friends.

• The physical processor starts choking under a massive overload.

• It physically can't keep up with the calculations for 50 servers at once.

• Your computer's ping to the server stays good (the network works), but the game server itself "freezes" inside for milliseconds.

⚠️ An important note about hosting support (disclaimer):

When you write to such a host's support: "Why is my server lagging and Var jumping?", you always get the template reply: "Everything is fine on our side, CPU load is normal, it's CS2 itself lagging after Valve's updates". They will never admit they sold your CPU thread to five other people.

🧱 The foundation of smooth CS2 (sub-tick):

Counter-Strike 2's new sub-tick system is extremely sensitive to uninterrupted calculation. The server has to read your actions every microsecond. If the host's processor gets "distracted" by other people's servers, sub-tick breaks. You shoot right at the model, see blood, but there's no damage — the server simply didn't process that hitbox in time.

📂 How we've solved this (honest ServUp):

We are firmly against overselling and value our project's reputation. We have a strict rule:

➔ 100% isolation: if your plan gives you 2 CPU threads, those threads belong only to your server, around the clock.

➔ No "neighbours": even if every other client on the machine starts tournaments at once, loads custom Workshop maps and fills servers with bots, your server won't even notice. Your Var and FPS will stay perfect.

🛠️ How to check and test a host:

1. Don't take a host's word for it — always ask for a trial during prime time (in the evening, 19:00 to 22:00).

2. Join the server with 10+ players online, open the game console and enter the telemetry command: cl_hud_telemetry_net_quality_graph_show 2.

3. Look at the network quality graph that appears: on oversold hosts you'll see constant yellow and red spikes (jitter and packet loss caused by CPU delays).

4. On our servers this graph stays perfectly flat and stable at any time of day. See for yourself with a free 1-day test!