Comprendre et corriger les chutes de TPS sur un serveur Minecraft

Minecraft server TPS is the single number that tells you whether your world is running smoothly or grinding through mob farms in slow motion. When ticks per second drop below 20, players notice instantly: rubber-banding, delayed hits, redstone lag. This guide breaks down what actually drives Minecraft server TPS and how to diagnose the real bottleneck with timings and spark reports instead of guessing.

What Actually Drives Minecraft Server TPS

Minecraft server TPS (ticks per second) reflects how many times the game loop completes each second. The target is 20 TPS, meaning one tick every 50 milliseconds. Everything that happens in the world — block updates, mob AI, redstone, entity physics — runs inside that single tick window on one thread. Understanding what fills that window is the first step to fixing lag.

Single-core clock speed matters more than core count

The Minecraft server, whether vanilla, Paper, Purpur or Forge, runs its main game logic on a single thread. Adding more CPU cores rarely helps that main thread; what helps is raw clock speed per core. A processor with high single-thread performance, such as a modern Ryzen chip, ticks the world loop faster than a processor with many slower cores. This is why CPU choice affects TPS more than RAM in most cases.

Chunk loading and generation

Every time a player crosses into unexplored terrain, the server has to generate or load chunks from disk. Chunk generation is CPU-intensive and can spike tick time noticeably, especially with complex world generation mods or large ore veins. Loading already-generated chunks from an NVMe drive is far less demanding than generating new terrain on the fly.

View distance and simulation distance

View-distance controls how many chunks are sent to clients; simulation-distance controls how many chunks are actively ticked (mobs move, crops grow, redstone runs) around each player. A high simulation-distance on a world with many players multiplies the number of chunks being ticked simultaneously, which is one of the most common causes of TPS drops.

Entity count

Mobs, item drops, minecarts, boats, arrows and villagers all count as entities that need AI or physics updates every tick. Uncapped mob farms, floating item stacks near hoppers, or large villager breeders can quietly push entity counts into the thousands, and each one adds a small slice of tick time that adds up fast.

If your current setup is limited by an underpowered CPU, moving to Minecraft server hosting built on high-frequency Ryzen CPUs and NVMe storage removes the hardware side of the equation, so you can focus purely on configuration and plugin tuning.

Diagnosing Minecraft Server TPS Drops with Timings and Spark

Guessing which plugin or mod is responsible for lag wastes hours. Two tools give you hard numbers instead: the built-in timings system on Paper-based servers, and the spark profiler, which works on vanilla, Paper, Forge and Fabric alike.

Reading /tps and watchdog warnings

/tps
TPS from last 1m, 5m, 15m: 19.8, 19.6, 20.0

If a single tick takes far longer than 50ms repeatedly, the watchdog thread will eventually kill the process and log a crash report pointing to the thread stack at the time of the freeze — a first clue, but not a full picture.

Timings reports

/timings report

The report breaks total tick time down by plugin, listener and even individual event handlers, showing what percentage of each tick a given piece of code consumes. Anything taking up more than a few percent of a single tick on its own is worth investigating.

Spark prof