1 Why game servers are weird

Most software scales across many cores. Game servers mostly don't. The "world tick" — mobs, redstone, physics, entities, scripts — runs on a single main thread, 20 times a second. Everything in that tick has to finish in 50 ms or the server falls behind (that's lag / low TPS).

Because that loop can only use one core at a time, the speed of a single core is what decides whether your server keeps up. Extra cores help with side jobs — chunk generation, networking, some async plugin work — but they can't make the main tick faster.

The one-line version: game-server performance ≈ how fast a single core is. That's "single-thread performance," and it's mostly clock speed × the CPU's per-clock efficiency (IPC).

2 Cores vs threads vs vCores

These three get used interchangeably in ads, but they're not the same thing:

TermWhat it really is
CoreA real, physical processing unit on the CPU. The thing that does the work.
ThreadA logical lane. With Hyper-Threading (Intel) / SMT (AMD), one core presents as two threads — but that's roughly a ~1.3× boost, not two full cores.
vCoreA "virtual core" a host assigns to your VPS/slice — usually mapped to one thread of a shared physical CPU. Its real speed depends entirely on which CPU and how oversold it is.

So "8 vCores" tells you almost nothing on its own. Eight vCores on a modern 5 GHz chip is great; eight vCores carved out of a 2.2 GHz server packed with 200 other customers is not.

3 Clock speed (GHz) — the number that matters

Clock speed is how many cycles a core runs per second. For a single-thread workload like a game tick, higher is better — directly.

  • Base vs boost: CPUs list a base clock and a higher "boost/turbo." What you care about is the speed it actually sustains under load.
  • Generation matters too: a newer architecture does more work per GHz (higher IPC), so 4.0 GHz on a 2024 chip beats 4.0 GHz on a 2014 one. But within reason, more GHz on a modern core = more TPS headroom.
  • The trade-off: server CPUs (Xeon/EPYC) have tons of cores but modest clocks (often 2–3 GHz). Desktop/"gaming" CPUs (Ryzen, Core i-series) have fewer cores but 5 GHz+. For one game server, the gaming chip wins.

4 The "more vCores" trap

Budget hosts love big core counts because they sound powerful and let them cram more customers per machine. But for a game server it's often the wrong spec:

  • A many-core server CPU at a low clock will hitch exactly where a few-core, high-clock chip sails through.
  • "Unlimited" or huge vCore counts usually mean a heavily oversold box — your "cores" are shared, so you get a fraction of them when the machine is busy.
  • What to do instead: ask the host which CPU model they run, then look up its single-thread benchmark. A higher single-thread score is what you want.

5 RAM — enough, not "more"

RAM holds your world and the running game in memory. You need enough, but past that, extra RAM does not raise performance — and on Minecraft, an oversized heap actually makes garbage-collection pauses worse.

ServerSensible RAM
Small vanilla/Paper, FiveM test, Rust solo2–4 GB
Community server (plugins, 20–60 players)4–8 GB
Modpacks, big RP, large Rust/ARK8–16 GB
Don't buy lag insurance in RAM. If your server lags at 8 GB, 16 GB usually won't fix it — the cause is almost always CPU or an unoptimized config, not memory.

6 Storage: NVMe matters more than you'd think

Game servers constantly load and save chunks/world data. Disk speed shows up as stutter when a new area loads or the world autosaves.

  • NVMe SSD — what you want. Fast, low-latency world I/O.
  • SATA SSD — fine, noticeably slower than NVMe under heavy saves.
  • HDD — avoid for game servers. Spinning disks stutter on chunk loads and big saves.

7 What to actually ask a host

  1. "What CPU model do you run?" Then check its single-thread benchmark. Vague answers ("high-performance Xeon") are a yellow flag.
  2. "NVMe storage?" It should be a yes.
  3. "Are cores dedicated or shared/oversold?" For consistent TPS you want real, non-throttled CPU time.
  4. "DDoS protection included?" Game servers get attacked; it should be standard.
  5. Honesty check: if the marketing leads with huge RAM and core counts but won't name the CPU, be cautious.

We lead with the spec that actually matters

Solace runs game servers on high-clock CPUs (the single-thread speed your TPS lives on), with NVMe storage and DDoS protection on every plan — and we'll tell you exactly what hardware you're on.

See our hardware

8 Quick recap

  1. Game servers run the main tick on one core — single-thread speed is king.
  2. Cores ≠ threads ≠ vCores; "8 vCores" means nothing without the CPU model.
  3. Few fast cores beat many slow ones for a game server.
  4. Buy enough RAM, not "more" — it won't fix CPU-bound lag.
  5. Insist on NVMe; avoid HDD.
  6. Ask for the CPU model and look up its single-thread score.

Related