TPS (Ticks Per Second)
Understanding TPS, the most important Minecraft server performance metric.
Illustrated procedure
Screenshots show the current application with demonstration data. Use your own service details; click an image to inspect it at full size.
Check the console
Open Essentials → Console. Check the current state, startup output and errors before making changes. Wait for Done or your software’s ready message before joining.

Enter a supported command
Use the command field beneath the console. Panel console commands normally omit the leading slash. This example uses the read-only command list; use commands supported by your core or plugin.

Check the command response
Press Enter once, then read the response in the console. Confirm the target and effect before sending an administrative command. Example output is not a performance measurement.

What Is a Tick?
Minecraft runs on a tick-based game loop. By default, the server attempts to process 20 ticks per second. Each tick is 50 milliseconds:
20 TPS = 50ms per tick = Optimal performance
18 TPS = ~55ms per tick = Minor lag noticeable
15 TPS = ~66ms per tick = Significant lag
10 TPS = 100ms per tick = Severe lag, near unplayableChecking TPS
Paper/Purpur
Run /tps in your server console to see TPS for the last 1, 5, and 15 minutes.
Spark
Install Spark and run /spark tps for detailed tick rate information.
What Causes Low TPS?
- Too many entities (mobs, items, villagers)
- Heavy plugins doing lots of work each tick
- Excessive redstone activity
- Large-scale block updates
- World generation (new chunks being created)
- Complex mod machinery
Fixing Low TPS
- Run
/tpsto confirm the issue - Use
/spark profilerto identify the cause - Reduce entity counts where possible
- Optimize or replace inefficient plugins
- Adjust view distance and simulation distance