What Actually Causes Minecraft Server Lag

Lag is the number one complaint in Minecraft server operation. It's also one of the most misunderstood. A lot of server owners assume lag equals bad hardware, and sometimes that's true — but more often it's something in the server configuration or world state that hardware can't fix, no matter how fast.

TPS and MSPT

The core metric to watch is TPS — ticks per second. Minecraft's game loop targets 20 TPS. Each tick should take 50ms. MSPT (milliseconds per tick) tells you how long each tick is actually taking. If MSPT consistently exceeds 50ms, your TPS drops below 20 and the server starts feeling sluggish. Everything in the game is tied to the tick rate — mob movement, redstone, crop growth, weather, player physics.

The most common culprits

• Entity count — Too many mobs, items on the ground, or minecarts. Each entity gets processed every tick.
• Chunk loading — Players exploring new terrain forces chunk generation, which is CPU and I/O intensive.
• Hopper chains — Hoppers are notoriously expensive. Large sorting systems can tank TPS on their own.
• Redstone clocks — Continuous redstone activity runs every tick. Unoptimised clocks are a common performance killer.
• Plugin overhead — A badly written plugin with a task running every tick can eat significant CPU headroom.

How to actually diagnose it

On Paper servers, the /timings report command gives you a detailed breakdown of what's consuming tick time. Spark is a better profiler if you want real-time data. Both will tell you whether the lag is coming from a plugin, entity processing, chunk operations, or something else. Random guessing at the cause is almost always slower than just pulling a timings report.

From our side as a host, we can see when a server's CPU usage is consistently high — that usually correlates with TPS issues. But the fix is almost always in the server configuration, not the hardware.