TPS and MSPT are the two numbers that tell you whether your server is healthy: TPS is how many times per second the world updates (20 is perfect), and MSPT is how many milliseconds each update takes (under 50 is healthy).
What TPS means
TPS stands for ticks per second. A tick is one update of the entire world: mobs move, blocks change, redstone fires. Minecraft-style servers aim for exactly 20 TPS. If your reading is a solid 20, the server is keeping up perfectly. Anything below 20 means the server is falling behind, and players will feel it as slow, laggy gameplay.
What MSPT means
MSPT stands for milliseconds per tick, or how long each single tick takes to finish. Here is the important link: to hit 20 TPS, each tick has to finish inside 50 ms (1000 ms divided by 20). So:
- MSPT well under 50: you have spare headroom, and TPS will stay at 20.
- MSPT creeping toward 50: you are near the edge, and any spike will drop TPS.
- MSPT above 50: the server cannot finish ticks in time, and TPS falls.
MSPT is the earlier warning sign. TPS can still read 20 while MSPT quietly climbs, so watching MSPT tells you about trouble before players notice it.
How to read them
- On Paper, Spigot, or Purpur, type /tps and /mspt in the Console tab or in-game.
- On recent vanilla versions, use /tick query to see the current tick time.
- For a deeper look, install the free Spark plugin and run /spark tps for a live readout or /spark profiler to find exactly what is eating your ticks.
You can run any of these commands straight from the input box at the bottom of the Console tab.
Reading the numbers
- 20.0 TPS and MSPT around 10 to 30: healthy, plenty of room.
- 20.0 TPS but MSPT near 45 to 50: healthy for now, but one more mob farm or player could tip it over.
- TPS below 18: something needs fixing today.
When MSPT spikes but TPS looks fine
Averages hide short spikes. If MSPT jumps every few seconds even though the average TPS is 20, you likely have a periodic cost such as autosaves, a scheduled task, or a chunk-loading burst. The Spark profiler is the fastest way to name the culprit.
Turning readings into fixes
Once you know your numbers, the fixes are the usual suspects: lower view distance and simulation distance, clear excess entities, remove a heavy plugin, or add RAM. You can upgrade RAM any time from the client area at guavahost.com/account with prorated billing, and it applies in seconds without touching your world. Re-check /tps and /mspt after each change so you can see what actually helped.
Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.