TPS vs FPS: understanding real Minecraft server performance
21 août 2026
"My server lags even though I have a top-end PC." This is one of the most common confusions among players who start administering a server: FPS (frames per second rendered by your screen) and TPS (ticks per second processed by the server) are two completely different measurements, and only the second one tells you whether the server actually has a problem.
What is a tick?
Minecraft runs its game logic (entity movement, redstone, crop growth, mob AI…) in "ticks". The server targets 20 ticks per second — that's the absolute reference. Below 20, everything visibly slows down: mobs move in jerky steps, doors take time to open, redstone becomes unpredictable. A client running 300 FPS connected to a server at 8 TPS will still feel like the game is "lagging".
What causes TPS to drop
- Too many active entities — poorly designed mob farms, oversized livestock pens, item stacks on the ground that never get cleaned up.
- Too many loaded chunks — several players exploring in opposite directions force the server to simulate a huge area at once.
- Complex redstone — fast-clock redstone loops consume a disproportionate amount of compute time relative to their size.
- Poorly optimized plugins or mods — a single plugin doing one heavy operation per tick can be enough to tank the entire server.
How to check your TPS
On a Paper/Purpur server, the /tps command shows the average over the last 5, 10, and 15 minutes. Below 18-19, there's a real issue worth investigating; below 10, players actively notice it. The Spark plugin (a profiler bundled with most modern distributions) goes further, precisely identifying which plugin, entity, or chunk is eating the most compute time — far more useful than a blind restart.
RAM, CPU, and TPS: three different things
Adding RAM doesn't fix a TPS problem caused by heavy game logic — RAM stores, it doesn't compute. TPS depends almost entirely on single-core CPU speed, because Minecraft's main game loop (the "tick loop") remains largely single-threaded even on the most optimized distributions. That's why our plans highlight a guaranteed CPU percentage rather than a raw core count — see the details on theinfrastructure page.