How to Fix Server TPS Lag
Fix TPS lag by using Spark profiler to find lag sources, reducing view distance, and optimizing entities and redstone.
Quick Fix
Install Spark profiler to identify the lag source. Common fixes: reduce view distance and kill excess entities.
Error Message
Can't keep up! Is the server overloaded?How to Fix
Install Spark profiler and run /spark profiler to find lag sources
Reduce view-distance and simulation-distance in server.properties
Set entity limits per chunk
Remove lag machines and excessive redstone
Optimize hopper chains or use hopper optimization plugins
Pre-generate the world to avoid lag from chunk generation
Use Paper or Purpur instead of vanilla server for better performance
Common Causes
- Too many entities in loaded chunks
- Expensive plugin or mod operations on the main thread
- Insufficient server hardware
- World pre-generation with too many chunks
- Redstone lag machines
- Excessive hopper chains
Diagnostic Steps
- Run /spark profiler for 60 seconds
- Check the report for what is consuming tick time
- Address the top consumers
- Monitor TPS with /tps or Spark
FAQ
What is good TPS?
20 TPS is perfect. 18+ is acceptable. Below 15, players will notice lag. Below 10 is unplayable.
What does 'Can't keep up' mean?
The server cannot process a full game tick within 50ms (20 TPS target). It is falling behind on updates.