How to Reduce Minecraft Server Lag: A Practical TPS Optimization Guide

TPS (ticks per second) is the heartbeat of your Minecraft server. A healthy server runs at 20 TPS; anything meaningfully lower means the world is falling behind real time. Here's how to fix it.

Step 1: Confirm It's Actually a TPS Problem

Run /tps (Paper/Spigot) or check your panel's resource graph. If TPS is consistently below ~18, you have a real server-side bottleneck — not just internet lag.

Step 2: Check the Usual Suspects

• Entity/mob overload — huge mob farms or animal breeding pens tank performance fast
• Redstone contraptions — large always-on circuits tick constantly
• Chunk loading — too many loaded chunks from spread-out players or chunk loaders
• View distance set too high for your hardware

Step 3: Switch to a Performance-Focused Server Jar

Vanilla is the slowest option. Consider:

Step 4: Tune Key Settings

• Lower view-distance and simulation-distance in server.properties
• Cap mob spawn limits in spigot.yml / paper-world-defaults.yml
• Use a plugin like ClearLag or a Paper equivalent to periodically clean dropped items

Step 5: Rule Out Hardware

If you've optimized the world and settings and TPS is still low, the server itself may be underpowered or oversold. Signs of a hardware issue:

• Lag gets worse during backups (shared/slow storage)
• Lag correlates with other tenants' peak hours (oversold CPU)
• RAM usage is fine but CPU graph is pinned at 100%

Software optimization has limits. If you've done everything above and TPS still drops, it's a hardware and provisioning problem, not a config problem.

The Fix

Start with the software tuning above — it solves the majority of lag issues for free. If the problem persists, move to a host with dedicated, high-clock CPU cores and NVMe storage built specifically for Minecraft, like the plans at RepublicNodes.