Direct answer

For a normal Paper/Vanilla-style server, prioritize strong per-core performance for the main tick workload, while still having enough additional cores for chunk workers, networking, plugins/mods, GC, and the operating system.

Why Task Manager can look “low”

On an 8-core/16-thread CPU, one busy logical CPU can represent only a small part of the overall utilization graph. If the Minecraft tick thread is saturated, server MSPT can rise even while the total CPU percentage looks low. Check the /spark tps output and capture /spark profiler start --timeout 600 while the slow period is happening; high FPS or low ping is not evidence that the server tick is healthy.

When more cores help

Extra cores support chunk workers, networking, garbage collection, the operating system, and plugins or mods that correctly use asynchronous work. They do not automatically speed up a single busy Paper tick thread. Compare real server performance under similar player activity, rather than choosing hardware by advertised core count alone.

Folia is different

Folia removes the single global main thread and ticks independent regions in parallel. Its official project documentation says servers with many spread-out players can benefit and recommends substantial core counts. That does not mean Folia automatically accelerates a single overloaded region.

Other CPU problems

  • Tick-bound workload: If spark shows heavy entity AI, chunk generation, redstone, or plugin listeners on the tick thread, fix that workload first; moving from four slow cores to more slow cores may not solve it.
  • Host throttling: On a VM or shared host, check CPU quotas, steal time and thermal/power limits. Consistently high MSPT with little Minecraft work in a profile can warrant investigating the host.
  • Workers competing: During large world-generation jobs, compare MSPT with the job paused. Avoid assigning all CPU capacity to chunk or GC threads.
  • Folia: Independent regions can run in parallel, but one overloaded region can still be slow. Test player distribution and region behavior before moving a production network.

References

These sources were checked while preparing this article. Performance behavior and configuration can change between Minecraft/server-software versions, so verify version-specific settings before applying them.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000