How to Diagnose Low TPS on a Minecraft Server

Direct answer

Minecraft targets 20 TPS. If TPS drops below 20 because tick processing is too slow, players may see delayed block breaks, slow mobs, delayed inventories, slow eating, and rubber-banding.

Use /spark tps or Paper's basic /tps//mspt checks, then capture a spark profile during the slowdown.

TPS vs MSPT

TPS is the result; MSPT is the work. A server can have a high MSPT spike without its longer-term TPS average immediately looking bad. Sustained MSPT above roughly 50 ms prevents a normal 20 TPS tick rate.

Do not confuse TPS with ping. High network latency can make one player feel laggy while server TPS remains healthy.

Confirm it is server tick lag

• If all players see game logic slow down at the same time and MSPT rises, investigate server workload.
• If only one player has delayed movement but TPS/MSPT are healthy, investigate ping, packet loss, or the player's connection.
• If only new terrain causes stutters, investigate chunk generation and storage.

Profile during the slowdown

/spark profiler start --timeout 600

Run the profiler during normal load. In the result, look for the branch that consumes the most time rather than focusing only on total CPU or RAM graphs.

Typical fixes

The right fix depends on the report: reduce or redesign high-cost farms/entities, pre-generate a bounded world if exploration is the problem, update or remove a problematic plugin/mod, lower simulation distance if too much world logic is active, or move to faster hardware when the tick thread is simply saturated by legitimate workload.

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.

• PaperMC: Commands — performance profiling
• PaperMC: Profiling
• spark documentation: Command Usage

Related articles