What is the best CPU for a Minecraft server host?

Why does single-core speed decide Minecraft server performance?

A Minecraft world gets 50 milliseconds per tick, and one core has to finish the work. The game ticks 20 times a second. In vanilla and Paper, each tick of a world runs on the server's main thread. When a tick takes longer than 50 ms, the server drops below 20 ticks per second and the whole world slows down.

Folia, a Paper fork, shows the contrast. Its README describes grouping loaded chunks into regions, each with its own tick loop on a thread pool, so no single main thread remains. Paper and vanilla have no such split.

Extra cores still earn their keep: chunk input and output, network threads, garbage collection, and more servers side by side. For one world, buy clock speed; for many worlds, buy cores at that clock speed.

Which CPUs in Lumenfer plans suit Minecraft?

Lumen 6, Lumen 8 and Lumen 16 have the highest single-core clocks; Lumen 24 and Lumen 32 trade clock for cores and memory. Clock and cache figures below are AMD's, read on 1 November 2026.

Is a Ryzen X3D CPU better for a Minecraft server?

Lumenfer sells no X3D chip, so test one before you pay extra for it. AMD's page for the Ryzen 9 9950X3D gives the same 16 cores and 5.7 GHz max boost as the AMD Ryzen 9 9950X. The difference is cache: 128 MB of L3 against 64 MB. Whether your worlds gain from it depends on plugins and world size, and we publish no benchmark. Our page on whether a Ryzen X3D server is better for game hosting goes further.

How much RAM and how many cores does each Minecraft server need?

Mojang publishes no per-player figure, so start from Paper's advice and measure. minecraft.net and Paper's guide both start the server with a 4 GB heap. Paper's flags guide recommends 6 to 10 GB whatever the player count, with -Xms equal to -Xmx. It adds that memory past a point brings little. On a shared machine, it leaves about 1 to 1.5 GB per server for overhead.

A working rule for a host: one busy world per physical core, and heap plus overhead per server in RAM. Keep a few GB for the system.

Folia is the exception for very large worlds. Its README says it runs best on at least 16 cores, not threads, with a sizeable player count. It asks you to keep allocated threads under 80% of the CPUs, and expects nearly every plugin to need changes. Lumen 16, with 16 cores / 32 threads, is our smallest plan that meets Folia's ideal.

Which settings cut Minecraft's CPU load the most?

Simulation distance and a pre-generated world. Paper's server.properties reference defines simulation-distance as how far from players living entities are updated: 3 to 32 chunks, default 10. view-distance sets how much world data the server sends, also 10 by default. Every chunk inside the simulation distance costs tick time.

Folia's README recommends pre-generating the world, so fewer chunk workers are needed. The same logic holds on Paper: generation is CPU work, and doing it before launch keeps it out of play time.

Where should a Minecraft host run its servers, and what about DDoS?

Near your players, behind protection you arrange yourself. Amsterdam (Netherlands), Reykjavik (Iceland), Zurich (Switzerland) and Bucharest (Romania): all five plans in all four cities, one price everywhere. That suits players in Europe; others are better served elsewhere. DDoS protection is limited to whatever the datacenter network applies by default; nothing further is promised.

For Java Edition, Cloudflare Spectrum supports Minecraft on its Pro and Business plans, one application each; Bedrock is not supported. A Velocity proxy can sit behind it. Velocity's security guide insists that only the proxy may reach the backend servers, enforced by a firewall. Our guide to starting a game server hosting business covers the rest, and all plans are on what a Lumenfer server costs.