Fixing "Can't keep up! Is the server overloaded?"
This legendary error message means your server took longer than 50ms to process a single tick. Here is how to fix it.
1. Pre-generate Your World
Exploration kills performance. The server has to generate chunks on the fly.
Solution: Install the Chunky plugin and run:
2. Lower View Distance
In server.properties, view-distance is the biggest performance eater.
- 10: Default. Heavy.
- 6-8: Recommended for balanced performance.
- 4: Potato mode. Extremely fast, but players can't see far.
Pro Tip: Use `simulation-distance` to reduce tick processing range while keeping visual view distance higher (if using Paper).
3. Profile with Spark
Don't guess. Measure.
- Install Spark plugin.
- Run
/spark profiler start. - Wait 10 minutes.
- Run
/spark profiler stop. - Click the link to see exactly which plugin or entity is lagging your server.
Reading the CPU graph: vanilla is single-threaded, modded is not
Your plan grants N CPU cores. The percentage in the panel is per-process across all cores. Vanilla Minecraft Java's main tick is single-threaded - sustained 95% of one core is the ceiling and means the world is doing more work than the simulation can keep up with. Modded servers (Forge, NeoForge, Fabric) spawn additional worker threads, so 150-400% on a heavy modpack is normal. The right question is "are we hitting the cgroup ceiling and being throttled?" not "is the percentage high?" See the cross-game CPU explainer for the throttling check and the save-tick guide for multi-dimension packs.
Looking for managed Minecraft server hosting? Supercraft runs Minecraft dedicated servers with daily backups, instant setup, and 5 region options. Plans from $5.99/mo.