Minecraft server operations
Performance
Measure lag and investigate its cause.
4 guides in this topic
Investigate Minecraft lag: TPS, MSPT, and “Can’t keep up”
Check tick times and investigate CPU, chunk, entity, and plugin problems.
Investigate lag with Spark Profiler in Paper and Docker
Record a profile while lag occurs and identify costly plugins, tasks, and server activity.
Configure view distance and simulation distance in Paper
Compare viewing distance and active simulation, then measure their effect on server load.
Minecraft exit code 137: check OOMKilled and memory limits
Exit code 137 means SIGKILL. Check OOMKilled, Java heap, and container limits to identify memory exhaustion.