Minecraft TPS Calculator

What Is TPS in Minecraft?

TPS stands for Ticks Per Second. Minecraft servers run a game loop that processes all world activity 20 times per second at full speed. Each tick handles mob AI, block updates, player actions, redstone circuits, and chunk loading. When the server cannot complete all work within 50 milliseconds per tick, TPS drops below 20 and the game world slows down, causing lag for all connected players.

How TPS Affects Your Gameplay

TPS directly controls how fast the game world runs. At 20 TPS, everything moves at normal speed. When TPS drops, every game mechanic slows down proportionally. Here is what different TPS levels feel like in practice:

What Causes Low TPS?

Low TPS is almost always caused by the server trying to do more work per tick than the hardware can handle. Here are the most common culprits:

• Too many entities: Every mob, dropped item, and armor stand takes CPU time. A single mob farm can spawn hundreds of entities and crush your TPS. Use entity limits in your server config to cap these.
• Chunk generation: When players explore new areas, the server must generate terrain, caves, structures, and biome data. This is extremely CPU-intensive. Pre-generating your world with Chunky eliminates this problem entirely.
• Heavy plugins: Some plugins run expensive operations every tick, like scanning all players, recalculating permissions, or logging events. A single bad plugin can consume 30-50% of your tick budget.
• Poor server configuration: Default Minecraft settings are not optimized for multiplayer. High view-distance, excessive mob spawns, and untuned entity activation ranges waste CPU on work that does not improve gameplay.
• Insufficient hardware: Minecraft's main game loop runs on a single CPU thread. If that thread cannot complete all work in 50ms, TPS drops. Fast single-thread performance matters more than core count or RAM amount.
• Redstone machines: Large redstone contraptions, especially piston-based farms and flying machines, generate massive amounts of block updates that the server must process every tick.

How to Check Your Server's TPS

There are several ways to monitor your server's TPS, from simple commands to detailed profiling tools:

Understanding MSPT vs TPS

While TPS tells you how fast the game runs, MSPT (Milliseconds Per Tick) tells you how much work the server does per tick. The relationship is simple: each tick has a 50ms budget (1000ms divided by 20 ticks). If the server completes a tick in 30ms, it has 20ms of headroom and TPS stays at 20. If a tick takes 60ms, the server falls behind and TPS drops to about 16.7 (1000 / 60).

MSPT is actually more useful than TPS for monitoring performance. TPS caps at 20 even if your MSPT is only 10ms, so you cannot see how much headroom you have by looking at TPS alone. An MSPT of 40ms means your server is technically at 20 TPS but has almost no margin. If player count increases or a redstone machine activates, that 40ms could spike to 55ms and suddenly TPS drops. Check MSPT with Spark or the /mspt command on Paper servers.

How to Improve Your Server's TPS

If your TPS is below 20, here are the most effective fixes, ordered from easiest to most impactful:

1. Optimize your config files: Use our Config Generator to create performance-tuned configs. Reducing view-distance from 10 to 7 alone can recover 2-4 TPS.
2. Switch to Paper or Purpur: If you are running Vanilla or Spigot, switching to Paper gives you async chunk loading, optimized entity ticking, and dozens of performance patches for free. Read our lag reduction guide for the full migration process.
3. Pre-generate your world: Install the Chunky plugin and generate a world border worth of chunks before players explore. This eliminates chunk generation lag entirely.
4. Audit plugins with Spark: Run a Spark profile and identify the top CPU consumers. Replace or remove any plugin that consistently uses more than 5-10% of your tick budget.
5. Limit entities: Add entity clear plugins, set mob caps in bukkit.yml, and add kill switches for large mob farms. Use entity activation ranges in paper-global.yml to reduce AI processing for distant mobs.
6. Use Aikar's JVM flags: Optimized Java garbage collection flags reduce GC pauses that cause periodic TPS spikes. These flags are specifically tuned for Minecraft server workloads.
7. Upgrade your hosting: If you have optimized everything and still see low TPS, your hardware is the bottleneck. A faster CPU with strong single-thread performance is the answer, not more RAM.

When to Upgrade Your Hosting

Configuration and plugin optimization can only take you so far. Here are the signs that your hardware is the bottleneck and it is time to upgrade:

• MSPT stays above 45ms even with an optimized config, low entity count, and minimal plugins. Your CPU cannot keep up.
• TPS drops during peak hours but is fine with 1-2 players. Your server is not scaling to your player count.
• Chunk generation causes 2-3 second freezes. Your CPU cannot generate terrain fast enough. Pre-generation helps, but a faster CPU solves it permanently.
• Out-of-memory errors or constant garbage collection. You have hit your RAM ceiling. Time for a plan with more memory.
• Spark profiler shows "idle" time near zero. The server has no headroom and any additional load will cause TPS drops.

Use our Hosting Cost Calculator to compare plans and find the best upgrade path for your budget. CraftRift's dedicated cores deliver consistent performance even during peak hours, and you can compare our specs against Shockbyte to see the difference.

Frequently Asked Questions