How much CPU does a Minecraft server need?
Minecraft is unusual among game servers: the world simulation runs on one main thread. That single core has to simulate every entity, tick every block update, run redstone, process AI and handle networking within a 50 ms budget, twenty times a second. Memory can be added and cores can be added, but the tick loop stays on one thread.
So the question is not "how many cores" but "how much work does the tick loop do". A five-player survival world barely uses a modern core. A busy ten-player world with a large plugin pack, big farms and a 12-chunk view distance can push a desktop-class core close to its limit.
Why one fast core decides tick health
Because the main thread is serial, single-thread performance is the number that matters. A CPU with fewer, faster cores will beat one with more, slower cores for the same workload — which is why high-clock desktop processors make such good Minecraft hosts, and why old shared hosting hardware struggles even with plenty of cores available.
This is the part most "how many cores" advice gets wrong. Sixteen slow shared cores will not fix block lag caused by a saturated tick thread. Reducing what the tick thread has to simulate will.
What PufferHost runs
Every PufferHost server gets one dedicated core — two threads — on a node running an AMD Ryzen 9 5900XT: 16 cores, 32 threads, boost clocks up to 4.8 GHz. That is a high-clock desktop-class part, whereas plenty of hosts still run older or shared CPUs where a busy node affects every server on it.
A dedicated core removes the noise of neighbours. Your tick time is your own workload, not the sum of whatever else happens to be running on the same physical CPU.
What actually costs tick time
Entities first: mob AI, pathfinding, item movement and hoppers are simulated every tick, and farms multiply them. Chunk loading second: generating terrain for a player who runs in a straight line is far more expensive than keeping a settled base ticking. Redstone and block updates third, particularly clock circuits that fire constantly.
Plugins then add their own scheduled work on top. Most are well behaved and cost almost nothing, but a single plugin that runs a heavy task every tick can outweigh the game itself. When tick time is high, plugins are usually the first thing to measure.
How to measure what your server is doing
MSPT — milliseconds per tick — is the honest metric. Under 50 ms means the server is holding 20 TPS; sustained time above it means dropped ticks, and that is what players experience as block lag, rubber-banding and delayed interactions. TPS alone is a lagging indicator, since it only drops once the ticks are already late.
On PufferHost you can read MSPT from the console, and our guides on reading server logs walk through the diagnostics. If MSPT spikes only while players explore, memory and chunk generation are involved — check the RAM calculator too.
Common questions
Is Minecraft CPU or RAM intensive?
Both, for different reasons. CPU decides whether the server can simulate the world smoothly inside the 50 ms tick budget; RAM decides whether it can hold the chunks, entities and plugins in memory without pausing for garbage collection. Lag caused by tick pressure feels constant, while memory pressure appears as spikes.
How many cores does a Minecraft server need?
One fast core does the world simulation, so core count is far less important than single-thread speed. Extra cores still help with chunk generation, garbage collection and any out-of-process work — but adding cores will not fix a saturated tick thread.
How many players can one CPU core handle?
On a modern high-clock core, a vanilla or Paper server usually stays inside its tick budget with ten to twenty players, depending on what those players are doing — and PufferHost’s free tier includes ten slots. Ten players in one redstone-heavy base cost far more than the same ten spread across a quiet world.
Why does my server lag with low CPU usage?
Because the tick loop is single-threaded. A server can report 10% total CPU usage while its main thread is completely saturated, with fifteen cores sitting idle. Watch MSPT rather than overall CPU percentage to see this.
Do plugins affect CPU more than players?
They can. Players cost a predictable amount each, spread across the tick. Plugins are open-ended: one that scans every entity every tick can cost more than the players it serves. When MSPT is high, measure per-plugin cost before assuming you need more hardware.
