CPU cores vs clock speed for game servers

Two hosting plans, same price. One offers 16 cores at 2.4 GHz, the other offers 4 cores at 5 GHz. For most game servers, the second one is the better buy. The reasons matter, and they aren't obvious.

The single-thread reality

Almost every popular game server you can rent runs its main simulation loop on one CPU core. Auxiliary work (network I/O, world saving, chunk generation, sometimes AI) may use other cores. The main tick almost never does.

This is true for:This is true for:

• Minecraft Java, both vanilla and Paper / Purpur (Paper is faster, still mostly single-threaded for ticks).
• Vintage Story.
• Valheim.
• Most older Source-engine games.
• 7 Days to Die.
• Project Zomboid.
• Eco uses multiple cores better than most, but still has a hot path.

Implication: the speed of your fastest single core is the upper bound on your server's tick budget. Once that core saturates, more cores cannot save you. The simulation loop cannot be parallelized just because you have spare cores sitting idle.

So why do hosts advertise many cores?

A few reasons:

• It looks impressive on a marketing page.
• It is true that more cores help if you run multiple servers on the same host. A modpack server, a Discord bot, a backup task, and a status checker can all use separate cores at once.
• It is true that more cores help with auxiliary work like chunk generation and saving.

But none of that makes your one tick-loop run faster. If your tick is the bottleneck, throwing 12 more idle cores at it changes nothing.

When more cores actually help

• You are hosting multiple game servers on the same machine.
• You run heavy mods that explicitly use multi-threading (rare).
• You are doing chunk pre-generation in parallel (Chunky benefits).
• You have many simultaneous players doing things that touch independent systems (network I/O, save I/O).

For one game server with one community, the diminishing returns kick in fast. The fourth core sees less work than the second. The eighth sees almost none.

When clock speed actually helps

• You are running a modpack with heavy automation (Create, AE2, mob farms).
• You are running Vintage Story with active bloomeries / firepits / production zones.
• You are running any game where the player count is approaching what the engine can handle.
• You feel any tick stutter that is not network-related.

In all these cases, more GHz is the difference between "fine" and "smooth."

A practical heuristic

If a host doesn't disclose the CPU clearly, that's a yellow flag. You don't need to know the exact part number. You do need to know "current generation, high boost clock" or "older Xeon optimized for density." Those are very different products at the same dollar cost.

What "current generation" buys you

Beyond raw clock speed, newer CPU generations bring:

• Better branch prediction (helps unpredictable game logic).
• Larger and faster caches (helps when working sets fit in L3).
• Faster memory subsystems (helps saves and chunk loads).

Two CPUs with the same nominal clock can differ 20 to 40 percent in real game-server performance based on generation. This is why the "GHz number" is a useful guide but not a perfect one. Modern boost clock plus modern architecture is the actual goal.

The two plans, side by side

The introductory example, fleshed out:

Spec	"Many cores" plan	"Fast cores" plan
Cores	16	4
Base clock	2.4 GHz	4.2 GHz
Boost clock	2.8 GHz	5.0 GHz
Single-thread benchmark	~1800	~3700
Best for	Many small servers on one box	One responsive server
Game-server feel	Mediocre under load	Smooth
Cost	Same	Same

For one game server, the fast-cores plan wins on every metric that affects players.

A quick decision tree

You are running one game server, want it to feel great:

• Pick the fastest-clock current-gen host you can afford.

You are running a small empire of bots, servers, and side projects:

• Take the higher core count, accept slightly lower per-core speed.

You don't know what you'll need yet:

• Default to clock speed. It hurts less to have idle cores than to have a saturated one.

The marketing trap

Cores are easy to count and sound impressive. Single-thread speed is harder to compare and sounds boring. Hosting marketing optimizes for the easy number. The right number for game servers is the boring one.

Read past the headline. Look for clock speed (boost), generation, and ideally a benchmark score. If the host is proud of those numbers, they'll show them. If they aren't, ask.