Home / Blog

How vCPU and RAM affect your game server, and what you pay for

Every hosting plan lists two numbers: RAM and vCPU. They do different jobs, and each game leans on them differently. Here's what they mean, so you can pick a plan that runs smoothly without paying for things that won't help.

RAM: how much the server can hold

RAM is the server's working space. It holds the world that's loaded around players, everyone's data, and every mod or plugin.

  • Too little RAM shows up as crashes, "out of memory" errors, and lag spikes every few seconds while the server frees up space.
  • More RAM than you need does nothing. A 4 GB vanilla server doesn't get faster at 8 GB.

What fills RAM is mostly mods and how much of the world is loaded, not just player count. Ten friends building one base use less than five friends exploring in five directions.

vCPU: how fast the server can think

A vCPU is one processor thread set aside for your server. The CPU runs the game itself: mobs, physics, redstone, hit registration.

The catch: most game servers do their main work on one thread. Minecraft runs its world in a single loop, 20 times a second. CS2 runs its match on one main thread, 64 times a second. If that one thread can't keep up, everyone lags, no matter how many cores sit idle.

So for most games, a fast core matters more than many cores. Extra vCPUs still help with the work around the main loop: generating new terrain, saving, and running plugins.

What each game needs

Minecraft

Minecraft is the most variable. Vanilla is light. Modpacks can need four times the RAM.

  • Vanilla, small group: 1 to 2 GB is plenty.
  • Lighter modpacks: around 4 GB.
  • Heavier modpacks (big tech or magic packs with 200+ mods): 6 to 8 GB, and an extra vCPU, since many mods add work to every tick.

Our Minecraft server plans use these sizes.

Running Paper instead of vanilla gets noticeably more out of the same hardware for plugin servers. (See our post on what Paper and Spigot mean.)

Counter-Strike 2

CS2 is the opposite of Minecraft: light on RAM, heavy on CPU. Maps are small and fixed, so 3 to 4 GB covers most servers. What costs more is player count and plugins, since every extra player adds work to that 64-times-a-second loop.

  • Scrims and 5v5 (up to 12 players): 3 GB, 2 vCPU.
  • Retake or deathmatch (up to 32): 4 GB, 2 vCPU.
  • Surf and custom modes (up to 62): 6 GB, 3 vCPU.

Our CS2 server plans use these sizes.

Valheim

Valheim's server is lighter than you'd expect, because the game shares the work with players' PCs. Whoever enters an area first runs the mobs and physics there. That's why one player with a bad connection can make an area lag for everyone near them, even on a strong server.

  • Vanilla, up to 10 players: 4 GB, 2 vCPU. Ten is the game's own cap.
  • Modded (BepInEx): 6 GB, for the extra headroom mods need.

Our Valheim server plans use these sizes.

RuneScape: Dragonwilds

Jagex gives a clear rule for its official dedicated server: 2 GB, plus 1 GB per player, up to 6 players.

  • 2 players: 4 GB.
  • Up to 4 players: 6 GB.
  • Up to 6 players: 8 GB.

Our Dragonwilds server plans use these sizes.

How this turns into price

RAM is the main thing a server costs to run, so hosts, including us, price mostly by RAM. vCPU rises with it on bigger plans, so heavy modpacks get the extra processing they need.

Setup is included in every price. All prices are launch prices.

Three ways to avoid overpaying

  1. Pick by what you run, not by player count alone. A heavy modpack for 3 friends needs more than vanilla for 10.
  2. Start smaller and move up. You only pay for the extra RAM once you know you need it.
  3. Don't chase cores. Two fast vCPUs beat eight slow ones for almost every game here.

Not sure which plan fits?

Tell us the game, the modpack and how many people play. We'll pick the plan, set it up for you, and check it runs well once your group is on. Try any game free for 1 day, no payment card needed.

Stuck? Ask us on Discord.

Keep reading

All posts