Minecraft ticks per second, or Minecraft TPS, is a key measure of server performance that affects every player experience. Understanding how TPS works helps server owners and players diagnose lag and choose stable hosting.
Below is a detailed overview of Minecraft TPS, including measurement, common issues, configuration, and troubleshooting.
| Metric | Ideal Value | Problem Threshold | Measurement Method |
|---|---|---|---|
| Minecraft TPS | 20.0 | Below 18 | Server console or monitoring plugin |
| Tick Time (ms) | 50 | Above 60 | Average tick duration over 100 ticks |
| MSPT (Milli-Ticks Per Tick) | 50 | Above 60 | Plugins like Spark or Timings |
| TPS Average (10 min) | 19–20 | Below 16 | External monitoring tools |
Understanding Minecraft TPS Metrics
What TPS Means for Server Performance
Minecraft TPS represents the number of game ticks completed each second, with 20 TPS meaning one tick every 50 milliseconds. TPS below 20 causes visible lag, delayed actions, and missed tick updates for entities and redstone.
How Tick Time Is Calculated
Each tick should take 50 ms on average. Tick Time measures the actual time taken per tick. If Tick Time consistently exceeds 50 ms, TPS drops because the server cannot keep up with real-time pacing.
Measuring TPS in Practice
Using Server Logs and Plugins
Server logs and metrics plugins display live and average TPS, along with spike details. Popular tools include Spark, Timings, and Paper’s built-in timings report for deep performance profiling.
External Monitoring Tools
External services track TPS graphs, alert on drops, and correlate lag with specific events or plugins. Reliable monitoring helps distinguish brief spikes from chronic performance issues.
Common Causes of Low TPS
Chunk Updates and Entity Count
High entity density and frequent chunk updates increase workload per tick. Overloaded chunks with mobs, tile entities, or active redstone can push MSPT beyond safe thresholds.
Heavy Plugins and Redstone Circuits
Some plugins run synchronous tasks or scan large areas each tick, while complex redstone contraptions trigger many block updates. Optimizing plugins and simplifying redstone often yields large TPS gains.
Optimizing Server Performance
Configuration and Hardware Tuning
Adjust view distance, simulation distance, and entity cramming limits. Allocate sufficient RAM, use fast storage, and select optimized server software such as Paper or Purpur for better throughput.
Ongoing Monitoring and Maintenance
Regular timings reviews, plugin updates, and periodic world cleanup reduce lag sources. Scheduling backups during low-traffic hours and monitoring long-term trends keep TPS stable.
Maintaining Reliable TPS Long Term
- Monitor TPS and MSPT daily with a trusted plugin or external tool.
- Review timings reports to identify costly plugins or redstone mechanisms.
- Limit entity density and optimize chunk loading zones.
- Keep server software, plugins, and libraries up to date.
- Allocate appropriate hardware resources and adjust game settings wisely.
FAQ
Reader questions
How can I check my server’s current TPS?
Use in-game server stats, console logs, or performance plugins like Spark to view live and average TPS values.
What TPS should I aim for in a multiplayer server?
Stable 20.0 TPS is ideal; consistently above 18 is acceptable for most gameplay, while below 16 indicates noticeable lag.
Does player count directly affect TPS?
More players generally increase entity and chunk activity, but TPS depends on total workload, including entities, redstone, and plugins.
Can world size influence Minecraft TPS?
Larger worlds with complex structures and active chunks can strain performance, especially if many chunks are loaded at once.