25% off on first order withAPEX25
Minecraft
Posted on Mar 27, 2022

Minecraft Server Can’t Keep Up

When the Minecraft server console prints Can't keep up! Is the server overloaded?, the server is struggling to process everything happening in the world fast enough. This is tick lag, and it affects every player on the server at the same ti...

When the Minecraft server console prints Can't keep up! Is the server overloaded?, the server is struggling to process everything happening in the world fast enough. This is tick lag, and it affects every player on the server at the same time. Understanding what triggers it is the first step to bringing performance back under control.

 

What Does “Can’t Keep Up” Mean?

Every Minecraft server runs on a tick cycle. The server targets 20 ticks per second (TPS) to keep movement, entity behavior, redstone, chunk generation, and all other world operations running smoothly. When the server cannot complete all those operations within the available time, ticks start queuing up and TPS drops below 20.

The console message looks like this:

Can't keep up! Is the server overloaded? Running 8567ms or 249 ticks behind

A TPS drop to around 15 is noticeable. Drops to 10 or lower cause significant lag for all players. At 5 TPS or below, the server is effectively unplayable. The important distinction is that TPS is not determined by how much RAM is allocated or how large the world is. It is determined by what is happening in the world right now.

 

Too Many Entities

Mob farms are one of the most common causes of tick lag. Chicken farms, iron golem farms, skeleton grinders, and similar builds are useful for gathering resources, but they concentrate large numbers of entities in a small area. The server has to process the AI, movement, and collision for every entity every tick.

Item drops from those farms compound the problem. Eggs, bones, rotten flesh, and other drops accumulate as entities in the world if they are not collected quickly. In large farms, item entities can outnumber the mobs themselves.

Other entity types contribute as well. Item frames, armor stands, and minecarts all take up processing resources. In extreme cases, a high entity count in a single chunk can produce ticking entity errors that crash the server. Reducing the number of active farms and setting mob caps lower through server settings are the most direct fixes.

 

Automatic Machines

Redstone machines and mod-based automated blocks add to the server’s per-tick workload. A single redstone clock running continuously is manageable, but dozens of them spread across the world or concentrated in one region add up quickly. The same applies to automated machinery from mods: conveyor belts, item pipes, generators, and similar blocks all require server-side processing.

Removing unused machines or consolidating them into fewer active builds reduces the per-tick load. For modded servers, checking whether specific mods expose performance-related config options is worth doing before making larger changes.

 

Poor Optimization Settings

If entity counts and redstone use are already low but tick lag persists, server configuration is the likely cause. Vanilla Minecraft servers do not expose many performance controls. Switching to Paper gives access to a much wider set of optimization settings for entity processing, chunk loading, and redstone behavior.

Key settings to review on a Paper or Spigot server include:

  • View distance: Lowering the number of chunks the server loads around each player reduces chunk generation and entity processing load. A value between 6 and 10 is a reasonable range for most servers.
  • Mob spawn limits: The spawn-limits settings in bukkit.yml control how many mobs of each type can exist per chunk. Reducing these caps lowers entity processing without disabling spawning entirely.
  • Entity cramming: The maxEntityCramming game rule limits how many entities can overlap in the same space. Lowering this value reduces processing in crowded mob farms.
  • Tick distance: On Paper, mob-spawn-range controls how far from players mobs can spawn, which can reduce the total number of entities in loaded chunks.

For modded servers, the equivalent controls are usually found in individual mod configuration files. Reading the server log when lag spikes occur can help identify which mods or chunks are responsible.

 

Conclusion

The Can't Keep Up message is a sign that the server’s tick budget is being spent faster than it can be replenished. Reducing entity counts from farms and machines, adjusting spawn limits, and lowering view distance cover the majority of cases. Servers still running on vanilla should consider switching to Paper for the additional configuration options. If tick lag keeps recurring, checking the server logs for specific warnings around entities or chunks can narrow down the source.

 

Why is my Server Lagging?
Reading Log Files
Why Won’t My Server Start?