Why More Cores Don't Make Your Minecraft Server Faster
Open any Minecraft hosting plan and the first spec you see is usually the core count. "12 dedicated cores!" "Up to 32 cores per server!" The numbers are designed to look impressive, and they usually do. Higher core count means a more powerful server, right?
For Minecraft specifically, this is wrong. Cores barely matter. The number that actually determines whether your server runs smoothly is single thread performance, which is the speed of one core, not the count of many. A server with one fast core will outperform a server with sixteen slow cores, every single time.
This article explains exactly why that is, why most hosts pile on core counts in their marketing anyway, and why we made the deliberate choice at Server Heron to give every customer one dedicated core on the fastest CPU we could buy.
What core count actually means
A modern CPU is built from multiple cores. Each core is essentially a small processor that can run instructions on its own. A CPU labeled "16 cores" has 16 of these little processors built onto one chip.
Most modern CPUs also support hyperthreading or simultaneous multithreading, which lets each core handle two threads of execution at the same time. A 16-core CPU with hyperthreading shows up as 32 "logical cores" to the operating system.
When you buy a server with "16 cores," you are usually getting 16 physical cores, and possibly 32 threads. Or, more accurately for shared hosting, 16 cores worth of CPU time slices that you split with other customers on the same physical machine.
In the abstract, more cores means more total compute. If your workload can use all the cores at once, you get roughly linear scaling. A 16-core CPU finishes a parallelizable job in roughly half the time of an 8-core CPU.
That last clause matters. The workload has to actually be parallelizable. If it cannot be split across multiple cores, extra cores sit idle and contribute nothing.
Minecraft falls firmly into the "cannot be parallelized" category.
Why Minecraft cannot use multiple cores for tick work
Minecraft's server runs the game world on what is called the main tick thread. Every 50 milliseconds, the main thread has to process all the entities, all the block updates, all the redstone, all the player input, and all the plugin events for the entire server. This is the tick loop, and it produces the TPS reading that determines whether your server runs smoothly.
(For a full explanation of TPS and why 20 is the target, see our article on Minecraft TPS explained.)
The main tick thread is single-threaded. Everything in it runs sequentially. The server cannot calculate redstone on core 1 while ticking entities on core 2. The code was not designed that way, and dozens of subsystems assume that other subsystems have already finished their work for the current tick.
This is not a bug. It is an intentional architectural choice that has been in Minecraft since 2009. Mojang has slowly chipped away at it (chunk generation now runs on a background thread, network I/O has its own threads), but the core gameplay loop, the part that actually determines whether your server lags, runs on one core.
When you put a 32-core CPU in a Minecraft server, 31 of those cores spend most of their time doing almost nothing. They cannot pitch in to help the main tick complete faster. They are just there.
This is why a server with one fast core will absolutely destroy a server with sixteen slow cores for Minecraft. The fast core runs the tick loop faster. The slow ones cannot help, no matter how many of them there are.
Where extra cores actually do help (a little)
To be fair, extra cores are not completely useless. They help in a few specific places. None of them are the place that matters most.
Chunk generation. When a player walks into ungenerated terrain, the server has to create new chunks. Modern Paper and Vanilla versions offload this work to a background thread pool. Extra cores can run chunk generation in parallel, reducing brief lag spikes when players explore.
Network packet handling. Player network traffic (chat, inventory updates, position packets) is processed on dedicated threads. With more cores, the server can handle more simultaneous network operations without queueing.
Logging and saving. Writing chunks to disk and writing log lines happens on background threads.
Plugin background tasks. Some well-written plugins offload work to async threads. Things like database lookups, web requests, and heavy calculations should not run on the main thread, and good plugins are aware of this.
Other servers on the same box. If a host runs many small servers on one big CPU, more cores let them share the box without stealing from each other. This is the only place where "32 cores" really matters in commercial hosting, and it benefits the host, not the customer.
Here is the kicker. None of these subsystems affect your TPS reading directly. The biggest win you can get from extra cores is faster chunk loading, which feels nice but does not fix the slow-motion problem of a server that lags during normal play. And those background tasks are almost always handled at the host level, not from each customer's individual core allocation.
For the actual moment-to-moment performance of your server, only the main tick thread matters. And it only uses one core.
The math: 1 fast core vs 16 slow cores
Let us put concrete numbers on this. Below are two real CPUs you might find in Minecraft hosting today.
| CPU | Cores | Base / Boost Clock | Single Thread (PassMark) |
|---|---|---|---|
| Intel Xeon E5-2670 v3 | 12 cores / 24 threads | 2.3 / 3.1 GHz | ~1,800 |
| AMD Ryzen 9 9950X | 16 cores / 32 threads | 4.3 / 5.7 GHz | ~4,650 |
The Xeon has nearly as many cores as the Ryzen, and at first glance the price-to-cores math might even look favorable. But the Ryzen's single thread score is more than 2.5 times higher.
For a Minecraft server, this means the Ryzen completes a single tick in less than 40 percent of the time the Xeon needs. The Xeon-hosted server will hit its 50 ms tick budget much sooner under load and start dropping TPS. The Ryzen-hosted server will keep up.
Even if the Xeon had 24 cores or 48 cores, it would still lose this race. The cores it has cannot help with the work that actually matters.
This is why hosts that advertise "12 dedicated cores" while running on old Xeon hardware are misleading customers. The core count is real. It just does not translate to Minecraft performance.
Why hosts pile on the cores in marketing
Marketing departments love core counts because the numbers are big and they look like value. "16 cores for $5/month!" sounds incredible compared to "1 core for $5/month."
The catch is that those 16 cores are almost never 16 dedicated cores. They are 16 cores worth of time-slice shared with several other customers on the same physical machine. When everyone is using their cores at once, you get a fraction of what was promised. The math says "16 cores," the reality says "the leftovers of 16 cores."
A second trick is conflating core count with thread count. A plan that says "16 cores" might mean 16 hyperthreads on an 8-core CPU. Hyperthreaded "cores" are not full cores. They are doubling the same hardware into two queues.
A third trick is bundling old hardware behind the impressive core count. A 16-core CPU from 2014 has a much lower per-core performance than a 4-core CPU from 2024. The marketing makes the older one look better, even though the newer one is the correct choice for Minecraft.
All of these tricks rely on customers not understanding that core count is not the spec that drives Minecraft performance. The hosting industry has cultivated this confusion for years because it makes their marketing easier and lets them oversell physical hardware.