{"id":25008,"date":"2026-10-18T13:01:30","date_gmt":"2026-10-18T13:01:30","guid":{"rendered":"https:\/\/atalnetworks.com\/?p=25008"},"modified":"2026-10-18T13:02:08","modified_gmt":"2026-10-18T13:02:08","slug":"minecraft-low-tps-troubleshooting","status":"publish","type":"post","link":"https:\/\/atalnetworks.com\/fr\/minecraft-low-tps-troubleshooting\/","title":{"rendered":"Fix Low Minecraft TPS with CPU, Chunk, and Plugin Checks"},"content":{"rendered":"

To fix low Minecraft TPS, measure tick duration during the slowdown, capture a spark profile, and identify the work delaying ticks. Check plugin tasks, entities, chunk activity, and CPU availability. Test one change on a recoverable copy, repeat the same workload, and confirm that gameplay and saving still work.<\/span><\/p>\n

Start with your server build, Java version, player activity, recent changes, and the time of each incident. These details help separate a busy farm from a plugin fault, memory pressure, or a host resource limit.<\/span><\/p>\n

This Minecraft low TPS troubleshooting guide focuses on Java Edition running Paper. We use a repeatable process: measure the problem, isolate its cause, check the result, and keep a working recovery path.<\/span><\/p>\n

Distinguish TPS from Network Lag<\/span><\/h2>\n

TPS means ticks per second.<\/b> It measures how often the server advances its game simulation. Minecraft normally targets 20 TPS, which gives the server an average processing budget of 50 milliseconds per tick.<\/span><\/p>\n

MSPT means milliseconds per tick.<\/b> A tick that finishes in 20 milliseconds leaves time before the next scheduled tick. It does not need to consume the full 50 milliseconds. Sustained processing above that budget reduces the achievable tick rate.<\/span><\/p>\n

TPS alone can hide short freezes. Check median, 95th-percentile, and maximum tick duration over the incident window. The 95th percentile shows the value at or below which 95% of recorded tick durations fall. A maximum identifies the slowest recorded tick, but does not show how often that delay occurred. See the <\/span>Spark explanation of TPS and MSPT<\/span><\/a>.<\/span><\/p>\n\n\n\n\n\n\n\n\n\n
Symptom<\/b><\/th>\nFirst check<\/b><\/th>\nWhat to investigate<\/b><\/th>\n<\/tr>\n<\/thead>\n
Mobs, block actions, and farms slow down<\/span><\/td>\nTPS and tick duration during the event<\/span><\/td>\nWork delaying the server tick<\/span><\/td>\n<\/tr>\n
Short freezes with normal average TPS<\/span><\/td>\nSlow-tick samples and timestamps<\/span><\/td>\nBrief processing or pause events<\/span><\/td>\n<\/tr>\n
Actions arrive late while tick metrics stay normal<\/span><\/td>\nPlayer latency and packet loss<\/span><\/td>\nNetwork route, server connection, or client connection<\/span><\/td>\n<\/tr>\n
One player sees choppy movement<\/span><\/td>\nClient FPS and render load<\/span><\/td>\nLocal graphics or client performance<\/span><\/td>\n<\/tr>\n
Terrain arrives slowly during travel<\/span><\/td>\nChunk activity and network conditions<\/span><\/td>\nGeneration, loading, delivery, or queues<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Ping measures connection delay. FPS measures client rendering speed. Neither is a substitute for server tick measurements.<\/span><\/p>\n

The number of affected players is a clue, not proof. One player can trigger expensive work in a particular area. A shared network problem can affect several players while the tick loop remains healthy.<\/span><\/p>\n

Prerequisites and Supported Versions<\/span><\/h3>\n

Use a supported Paper release and the Java runtime required for that release. At the documentation check for this draft, Paper lists Java 25 for 26.1 and newer. Confirm the requirement for your exact build in <\/span>Paper’s setup documentation<\/span><\/a>.<\/span><\/p>\n

Paper includes spark from version 1.21 onward. Its documentation favors spark over the older Timings workflow. Check the startup log before installing a second copy. Commands and settings here should not be applied unchanged to Bedrock, Folia, or modded server platforms. See <\/span>Paper’s profiling guidance<\/span><\/a>.<\/span><\/p>\n

Before testing, prepare:<\/span><\/p>\n