What Is MSPT in Minecraft? Server Performance Explained
MSPT means milliseconds per tick. It is one of the most useful numbers for understanding Minecraft server performance because it tells you how long the server takes to calculate each game tick. If MSPT is too high, TPS drops and players feel lag.
MSPT vs TPS
Minecraft aims to run 20 ticks per second. That gives the server 50ms to complete each tick.
- 20 TPS / under 50 MSPT - healthy
- 18-20 TPS / 50-60 MSPT spikes - usually playable but not perfect
- Under 18 TPS / 60ms+ MSPT - noticeable lag
- 100ms+ MSPT - severe lag, rubber-banding, delayed blocks, slow mobs
TPS tells you the outcome. MSPT tells you how close you are to the limit.
What causes high MSPT?
Entities
Mobs, villagers, item piles, hoppers, farms, and pathfinding all cost tick time. Villager trading halls and mob farms are common MSPT killers.
Chunks
High simulation distance means more chunks ticking around players. Chunk loading and generation also hit CPU and disk.
Plugins and mods
Some plugins run expensive tasks every tick. Modpacks can add machines, dimensions, AI, pipes, and tile entities that keep ticking forever.
Garbage collection
If the JVM pauses to clean memory, MSPT spikes. That is where good Java flags and enough RAM matter.
Weak CPU
Minecraft needs strong single-thread speed. If the main thread is slow, no setting can fully hide it.
How to measure MSPT
Use Spark. It works on Paper, Fabric, Forge, and many modded setups.
Common commands:
/spark health
/spark profiler start --timeout 60
/spark profiler open
Look for the average MSPT and the worst tick spikes. If a plugin, mod, entity type, or block entity dominates the profile, you have a real target.
How to lower MSPT
- Lower simulation distance before render distance.
- Reduce entity-heavy farms and villager counts.
- Use Paper/Purpur optimisations for plugin servers.
- Add Fabric performance mods such as Lithium and FerriteCore where compatible.
- Pre-generate worlds to avoid live chunk generation.
- Tune Java flags and avoid tiny heaps on modpacks.
- Move to faster CPU hardware if the main thread is maxed.
Healthy targets
For a public server, aim for under 35ms average MSPT so you have headroom for spikes. For a private SMP, under 45ms is usually fine. Large modpacks may spike, but they should not sit above 50ms constantly.
Hosting matters
A host can give you enough RAM but still put you on weak or oversold CPU. That produces bad MSPT even when memory looks fine. Our Minecraft hosting uses Ryzen hardware and NVMe SSD, and the plan selector helps you match RAM and CPU to the server type instead of guessing from player count alone.
Bottom line
MSPT is the server's real workload number. Keep it below 50ms to hold 20 TPS, profile with Spark, reduce ticking entities and chunks, and use hardware with strong single-core performance.
Fighting MSPT lag? → View Space-Node Minecraft hosting - Ryzen CPU, NVMe SSD, and plan sizing built around real server workload.
