Minecraft Performance & Lag Reduction
Achieve a rock-solid 20.0 TPS. Learn how to profile entity bottlenecks, optimize Paper configuration files, and eliminate garbage collection pauses.
1. TPS vs Ping: Diagnosing the Root Cause
Server Lag (TPS < 20.0):
Caused by excessive mob farms, unoptimized redstone, or runaway chunk generation. All players experience slow block breaks and delayed mob reactions.
Network Latency (High Ping ms):
Caused by ISP routing or Wi-Fi packet drops. Check your ping to our Noida node. If TPS is 20.0 but ping is high, see our Latency Guide.
2. Pinpointing Lag with Spark Profiler
Install the free Spark profiler plugin from the Plugin Manager. In your console, run:
spark profiler start
# Let the server run under active player load for 5 minutes
spark profiler stopSpark generates a web link showing exact millisecond CPU breakdowns per plugin, entity type, and world region.
3. paper-world-defaults.yml Entity Tuning
Open config/paper-world-defaults.yml in your File Manager and apply these proven optimizations:
entities:
behavior:
despawn-ranges:
monster:
soft: 28
hard: 64
spawning:
despawn-ranges:
ambient:
hard: 56
soft: 28
chunks:
auto-save-interval: 6000
max-auto-save-chunks-per-tick: 124. Pre-Generating Chunks with Chunky
Generating chunks on the fly when players explore with Elytras is the #1 cause of sudden TPS collapse. Install Chunky and pre-generate your world border:
worldborder set 5000
chunky world world
chunky shape circle
chunky radius 5000
chunky start5. Verifying Aikar’s JVM Garbage Collection
All OrynCloud Minecraft nodes have Aikar’s G1GC Flags injected by default into your startup variables. These flags balance garbage collection pauses across multiple cores, eliminating 500ms freeze spikes.