How to Fix Minecraft Server Lag (TPS, Not Ping)

“Lag” gets blamed on the network, but on a server it’s usually TPS — ticks per second. A healthy server runs at 20 TPS; when it drops, everything feels rubbery for everyone. Here’s how to diagnose and fix it.

TPS vs ping — know which you have

Ping is the round-trip between a player and the server (network). TPS is how fast the server simulates the world (CPU). If everyone lags at once, it’s TPS; if one player lags, it’s their connection. Fixing the wrong one wastes hours.

Find the cause with a profiler

Run /tps and, on Paper/Purpur, use the built-in spark profiler (/spark profiler) to see exactly what’s eating tick time. Guessing is the slow way; a profiler points straight at the culprit.

The usual culprits

• Too-high view/simulation distance — the single most common cause.
• Hopper-heavy redstone and giant mob farms.
• Heavy or badly-written plugins (and too many of them).
• Chunk-loading from constant exploration or chunk-loaders.

Fixes that work

1. 1Use Paper or Purpur, not vanilla — their optimizations and config tuning matter more than any single setting.
2. 2Lower view-distance and simulation-distance to sane values (6–8).
3. 3Cap entities/mobs per chunk in the server config.
4. 4Pre-generate the world so exploration doesn’t generate chunks live.
5. 5Remove or replace the plugin the profiler flagged.

When it’s the host, not you

If you’ve tuned everything and TPS still sags under light load, the host’s CPU is too slow. A modern high-clock CPU is what holds 20 TPS — which is exactly what to look for when picking a host.