How to Tell If a Game Server Host Is Overselling RAM and CPU

A game server host is overselling when it sells more memory or CPU time than its physical machines can deliver to everyone at once, betting that most servers sit idle. You can usually tell by the pattern: lag that appears at the same busy hours every evening while your own server's memory use looks normal, tick rate drops with only a few players online, and the server's own performance tools blaming the CPU when your world is small. The fix is to measure it, report it with numbers, and move if the host does not act.

What overselling actually is

A physical server in a data center has a fixed amount of RAM and a fixed number of CPU cores. A host splits that machine into many game servers. Overselling means the total sold is larger than what exists.

There are two kinds, and they behave differently.

CPU overselling is everywhere and not always a problem. Most game servers sit near idle most of the day, so sharing cores works fine until many servers on the same machine get busy at once. Then everyone fights for the same cores and every server on the machine slows down. This is often called a noisy neighbor problem.

RAM overselling is more dangerous. If a host promises 8 GB to twenty servers on a machine with 128 GB, it works until enough of those servers actually use their memory. Then the machine starts swapping to disk or the system kills processes, which for you means sudden crashes with no error in the game log.

Signs your host is overselling

None of these proves it alone, but three or four together are a strong hint.

1. Lag follows the clock, not your players. The server runs well at 10 AM and stutters at 9 PM, even when the same three friends are online. Evening is when every other server on the machine is busy too.
2. The server is slow with nobody doing anything. An idle world should barely use the CPU. If it still reports lag, something outside your server is taking the time.
3. Crashes with no error. The console just stops, or the server restarts with nothing in the log about running out of memory inside the game. That can mean the operating system killed the process because the whole machine ran out of memory.
4. Load times change a lot from day to day. Disk contention shows up as world loading that takes one minute today and four tomorrow.
5. Very cheap "unlimited" plans. The lower the price per GB and the vaguer the limits, the more servers have to share each machine for the business to work.
6. Support says "upgrade your plan" when your usage is low. If your server uses 3 GB of a 6 GB plan and support's only answer to lag is a bigger plan, the plan size is not the problem.

How to measure it yourself

Game hosts do not give you a shell to run system tools, so use what the game gives you.

Minecraft

Install the spark profiler plugin or mod. Run these in the console:

spark tps
spark health
spark profiler start --timeout 300

spark tps shows ticks per second and how long each tick takes (MSPT). A healthy server sits at 20 TPS with MSPT well under 50. If MSPT spikes while the profiler shows no single heavy plugin, entity farm or chunk loading to blame, the server is waiting on the CPU, not doing extra work. The console line "Can't keep up! Is the server overloaded?" at quiet times points the same way.

Rust

In the console, run:

perf 1

Server FPS that drops sharply at the same time each evening with the same player count points at the machine, not your map. See why your game server is lagging for game specific causes to rule out first.

Any game

Keep a simple log for a week: date, time, players online, and whether it lagged. Write down the RAM use your control panel shows at those moments. If lag clusters around the same hours and your memory is not near the limit, you have a pattern you can show support.

Rule out your own causes first

Before blaming the host, make sure it is not one of these, because they look the same from the outside:

• Not enough RAM for your world. If memory use sits at the plan limit, the server is short on memory, not oversold. How much RAM a game server needs has numbers by game.
• A heavy mod or plugin. One badly written plugin can eat a whole core. A profiler finds it.
• World growth. Big redstone builds, hundreds of tamed creatures in ARK or giant factories in Satisfactory make a server heavier over time.
• Distance. High ping is about location, not overselling. See how to pick a server location for low ping.

What to do if you think your host is overselling

1. Collect numbers. TPS or server FPS, times, player counts and memory use from your log.
2. Open a ticket with those numbers. Ask directly whether the machine is under heavy load at those times and whether they can move your server to a less busy one. Our guide to writing a support ticket that gets answered has a template.
3. Give it a few days. A good host moves you or fixes the machine. A host that only offers upgrades is telling you something.
4. Leave with your world. Take a backup, download it, and move to a new host.

How to avoid it when buying

• Pick hosts that state RAM per plan and do not sell "unlimited" resources.
• Be wary of prices far below everyone else's per GB.
• Use the refund window to test at peak hours, not just right after you buy.
• Read red flags when choosing a host before you pay.

At GamezServers each plan states its RAM and vCPU and is priced at about 2.50 USD per GB a month. If performance is off, email support@gamezservers.com with your numbers and we will look at it, and you can change plans or cancel from the panel at any time. You can see the plans for every game on the games page.

FAQ

Do all game server hosts oversell?

Most share CPU cores between servers, because game servers are idle most of the time and it keeps prices low. That sharing only becomes a problem when the host packs so many servers on a machine that they slow each other down at busy hours. Memory overselling is less common and more harmful.

Can overselling cause my server to crash?

Yes, if it is memory. When the whole machine runs out of RAM, the operating system kills processes, and your server can stop without any error in the game's own log.

How do I prove my host is overselling?

You usually cannot prove it from inside your server, but you can show a pattern: lag at the same hours each day, low memory use on your side, and a profiler that shows no heavy plugin or build. That is enough for any good host to investigate.

Is a dedicated machine the only way to avoid it?

No. A well run shared host with fair limits works fine for most groups. A dedicated machine or VPS only makes sense for very large communities, and then you take on all the admin work yourself.