Minecraft server operations
Performance
Practical diagnostics for lag, TPS, MSPT, Spark reports, and safe Paper tuning choices.
4 guides in this topic
Minecraft Server Lag Explained: TPS, MSPT, and 'Can’t Keep Up'
This guide explains what TPS and MSPT actually mean, why “Can’t keep up” appears in the console, and which checks help you separate CPU, chunk, entity, and plugin problems quickly.
Use Spark Profiler to Find Minecraft Lag in Paper and Docker
Paper bundles Spark starting with 1.21, which makes it the preferred profiler for diagnosing lag. This guide shows how to capture a useful report and how to read the first findings without guesswork.
View Distance vs Simulation Distance: Safe Starting Values for Paper
Paper exposes view-distance and simulation-distance separately, which makes them one of the safest first levers for performance tuning. This guide explains what each setting changes and which starting values are sensible.
Minecraft Docker Exit Code 137: Diagnose OOMKilled Correctly
Exit code 137 means SIGKILL, not automatically an out-of-memory event. Confirm Docker OOMKilled state, compare JVM heap with container limits, and leave non-heap headroom.