Improve performance

TPS and MSPT in plain language#

Minecraft aims for 20 TPS—twenty game ticks each second. One tick has a 50 ms budget. MSPT is the time the server spends calculating a tick. Below 50 ms usually keeps 20 TPS; sustained values above 50 force the game to slow.

High network ping delays a player’s messages but does not automatically lower TPS. Low TPS affects everyone’s mobs, blocks and redstone. Diagnose the kind of lag before changing settings.

A useful order of checks#

1. 1
   Ask whether every player is affected and whether movement or game logic is slow.
2. 2
   Check TPS/MSPT with a compatible monitoring mod or Crafty metric.
3. 3
   Look at RAM without assuming “100% allocated” means out-of-memory.
4. 4
   Check per-core CPU use and temperature; overall CPU can look low while one core is full.
5. 5
   Watch disk activity and free space.
6. 6
   Remove or roll back newly added mods after a backup.
7. 7
   Reduce simulation-distance, then view-distance.
8. 8
   Pregenerate a bounded world so exploration is not creating chunks live.
9. 9
   Inspect huge farms, item piles, villagers, chunk loaders and redstone.
10. 10
    Make a backup, then restart normally and compare.

What each resource changes#

CPU single-core speed limits tick work. RAM holds loaded chunks and mod data, but allocating all system memory starves ZimaOS and file cache. SSD speed helps saves, backups and chunk reads. Entity count, farms and redstone increase tick work. Upload and routing affect outside players’ latency.