That dreaded “Can’t keep up! Is the server overloaded?” message in your console means your Minecraft server is struggling to process game ticks within the allocated 50-millisecond timeframe. When tick processing takes longer than this threshold, the server falls behind, causing lag, block placement delays, and frustrated players.
The “Can’t keep up” error occurs when your server’s tick rate drops below 20 TPS (ticks per second), indicating performance bottlenecks that need immediate attention. This comprehensive guide covers proven fixes to restore your server’s performance and eliminate these warnings permanently.
Understanding Server Tick Performance
Minecraft servers operate on a tick-based system where each tick represents 50 milliseconds of game time. During each tick, the server processes player actions, mob AI, redstone circuits, chunk loading, and world generation. When these processes exceed the 50ms window, you’ll see the infamous “Can’t keep up” message.
Normal server performance indicators:
- TPS (Ticks Per Second): 20 TPS optimal
- MSPT (Milliseconds Per Tick): Under 50ms ideal
- Memory usage: Consistent without frequent spikes
- CPU usage: Below 80% during peak hours
Performance degradation typically stems from insufficient hardware resources, poorly optimized server configurations, or resource-intensive modifications and plugins.
Hardware and Memory Optimization
RAM Allocation and Garbage Collection
Improper memory allocation causes frequent garbage collection pauses, directly triggering “Can’t keep up” errors. Most servers need 2-8GB RAM depending on player count and modifications.
Optimal JVM arguments for different server sizes:
For 4GB allocation:
-Xmx4G -Xms4G -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20
These flags enable G1 garbage collection with optimized pause times, reducing tick delays caused by memory cleanup operations.
CPU Performance Considerations
Minecraft’s single-threaded nature means CPU clock speed matters more than core count. Look for processors with high single-core performance, typically 3.5GHz or higher for optimal results.
Server hardware recommendations:
- Vanilla servers: 2-4GB RAM, 3.0GHz+ CPU
- Modded servers: 6-12GB RAM, 3.5GHz+ CPU
- Large networks: 16GB+ RAM, enterprise-grade processors
Server Configuration Tweaks
server.properties Optimization
Several server.properties settings directly impact performance and can reduce “Can’t keep up” frequency:
view-distance=6 – Reduces chunk loading overhead
simulation-distance=4 – Limits active chunk processing
max-players=20 – Prevents overloading
spawn-protection=0 – Eliminates unnecessary calculations
Lowering view distance from the default 10 to 6-8 chunks significantly reduces server load while maintaining playable experience.
Paper/Spigot Performance Settings
Paper and Spigot servers offer additional configuration options in paper.yml and spigot.yml:
Key paper.yml optimizations:
- max-auto-save-chunks-per-tick: 8
- optimize-explosions: true
- mob-spawner-tick-rate: 2
- container-update-tick-rate: 3
Essential spigot.yml tweaks:
- mob-spawn-range: 4
- entity-activation-range: reduced values
- tick-inactive-villagers: false
- nerf-spawner-mobs: true
Plugin and Mod Management
Identifying Performance Culprits
Use timing reports to identify problematic plugins consuming excessive tick time. Run /timings report on Paper servers or install performance monitoring plugins like Spark.
Common performance-heavy plugins include:
- Poorly coded economy plugins
- Excessive world protection systems
- Unoptimized custom plugins
- Multiple overlapping functionality plugins
Remove or replace plugins showing consistently high milliseconds per tick in timing reports.
Modded Server Considerations
Modded servers face unique challenges with “Can’t keep up” errors. Create mod servers and other technical modifications require careful resource management.
Limit resource-intensive mods like:
- Complex automation mods
- Excessive world generation modifications
- Poorly optimized content mods
- Multiple overlapping tech mods
World and Chunk Optimization
Pregeneration and Chunk Loading
Pregenerate your world using plugins like WorldBorder to eliminate on-demand chunk generation lag. This prevents “Can’t keep up” errors caused by players exploring new terrain.
Set reasonable world borders:
- Small servers: 5,000×5,000 blocks
- Medium servers: 10,000×10,000 blocks
- Large servers: 20,000×20,000 blocks
Entity and Redstone Management
Excessive entities and complex redstone contraptions cause significant tick lag. Implement entity limits and educate players about performance-friendly building practices.
Recommended entity limits per chunk:
- Animals: 15-20
- Monsters: 10-15
- Items: 50-100
- Villagers: 5-10
Professional Server Hosting Solutions
If optimization efforts aren’t resolving your “Can’t keep up” errors, consider upgrading to dedicated game server hosting. Professional Minecraft hosting provides optimized hardware and configurations designed specifically for game servers.
Ready to eliminate server lag permanently? GameTeam.io offers high-performance Minecraft hosting starting at $1/GB with 20% off for new customers. Our optimized servers prevent “Can’t keep up” errors with enterprise-grade hardware and expert configurations.
Monitoring and Maintenance
Performance Monitoring Tools
Regular monitoring helps prevent “Can’t keep up” errors before they impact gameplay:
- Spark – Comprehensive profiling and performance analysis
- LagGoggles – Visual lag source identification
- ServerTuner – Real-time performance metrics
- Built-in /tps command – Quick TPS checking
Scheduled Maintenance Tasks
Implement automated maintenance to prevent performance degradation:
- Automatic restarts every 12-24 hours
- Regular world saves and backups
- Periodic plugin cache clearing
- Log file rotation and cleanup
For persistent connection issues alongside performance problems, check our server connection troubleshooting guide for comprehensive solutions.
Frequently Asked Questions
Why does my server show “Can’t keep up” with low player counts?
Low player count doesn’t guarantee good performance. Automated farms, complex redstone, chunk loading, and background processes can overload servers regardless of active players. Check for hidden performance drains using timing reports.
How much RAM should I allocate to prevent these errors?
Vanilla servers typically need 2-4GB, while modded servers require 6-12GB. Avoid over-allocation as excess RAM can actually hurt performance by increasing garbage collection times.
Can switching to Paper or Fabric improve performance?
Yes, Paper offers significant performance improvements over vanilla Spigot through optimized algorithms and additional configuration options. Fabric with performance mods like Lithium and Phosphor also provides substantial benefits.
Should I worry about occasional “Can’t keep up” messages?
Occasional messages during world generation or server startup are normal. Consistent messages during regular gameplay indicate performance issues requiring attention.
Do view distance reductions significantly impact gameplay?
Reducing view distance from 10 to 6-8 chunks dramatically improves performance with minimal gameplay impact. Most players won’t notice the difference, but server performance will improve substantially.
Eliminating “Can’t keep up” errors requires a systematic approach combining hardware optimization, configuration tuning, and ongoing maintenance. Start with the most impactful changes like memory allocation and view distance reduction, then progressively implement additional optimizations based on your server’s specific needs.
