Skip to main content

Performance Problems

Server running slow? Here’s how to diagnose and fix performance issues.

Identifying Performance Issues

Symptoms

  • Players experiencing lag
  • Slow block breaking/placing
  • Mob/entity stuttering
  • Long loading times
  • Server crashes

Checking Server Performance

TPS (Minecraft)

TPS = Ticks Per Second (target: 20) Check with /tps command:
TPSStatus
20Perfect
18-19Good
15-17Noticeable lag
Less than 15Significant lag

Resource Monitoring

In your panel, check:
  • CPU Usage - Should be under 80%
  • RAM Usage - Should be under 90%
  • Disk Usage - Should have free space

Common Causes & Solutions

1. Not Enough RAM

Symptoms:
  • Out of memory errors
  • Frequent garbage collection pauses
  • Crashes when loading chunks
Solutions:
  1. Upgrade server plan
  2. Remove memory-heavy mods
  3. Reduce view distance
  4. Lower entity limits

2. Too Many Entities

Symptoms:
  • Lag in certain areas
  • TPS drops during farming
  • Entity-related errors
Solutions:
  1. Reduce mob spawn limits in config
  2. Clear excess entities: /kill @e[type=!player]
  3. Set entity limits per chunk
  4. Use mob stacking plugins

3. Chunk Loading Lag

Symptoms:
  • Lag when exploring new areas
  • Freezing during teleports
Solutions:
  1. Pre-generate world with Chunky (MC)
  2. Reduce view distance
  3. Reduce simulation distance
  4. Upgrade RAM

4. Heavy Mods/Plugins

Symptoms:
  • Lag correlating with specific features
  • High CPU usage
Solutions:
  1. Profile with Spark (MC) or similar
  2. Identify problematic mods/plugins
  3. Remove or replace heavy ones
  4. Optimize mod configs

5. World Size Too Large

Symptoms:
  • Slow backups
  • High disk usage
  • Loading delays
Solutions:
  1. Set world border
  2. Delete distant chunks
  3. Limit world exploration
  4. Regular cleanup

6. Redstone/Hopper Lag (MC)

Symptoms:
  • Lag near complex contraptions
  • TPS drops in certain chunks
Solutions:
  1. Limit hopper usage
  2. Optimize redstone designs
  3. Use hopper alternatives
  4. Configure paper/spigot hopper settings

7. Poor Configuration

Symptoms:
  • Generally poor performance
  • Default settings not optimized
Solutions:
  1. Follow optimization guides:
  2. Adjust view/simulation distance
  3. Configure entity limits
  4. Enable async operations

Quick Optimization Checklist

Minecraft

  • Use Paper instead of Spigot/Vanilla
  • View distance: 8 or lower
  • Simulation distance: 6 or lower
  • Monster spawn limit: 50 or lower
  • Entity activation range reduced
  • Pre-generate world
  • Optimize JVM flags

General

  • Adequate RAM for your use
  • Regular restarts scheduled
  • Old logs cleaned up
  • Backups managed
  • Unused mods/plugins removed

Profiling Tools

Spark (Minecraft)

  1. Install Spark plugin
  2. /spark profiler start
  3. Wait during lag period
  4. /spark profiler stop
  5. Analyze report

Built-in Timings (Paper)

  1. /timings on
  2. Wait 10-15 minutes
  3. /timings paste
  4. Review report

Performance Settings Reference

Server.properties (MC)

view-distance=8
simulation-distance=6
max-players=20

Paper-world-defaults.yml

chunks:
  auto-save-interval: 6000
entities:
  spawning:
    spawn-limits:
      monsters: 50
      animals: 8

When to Upgrade

Consider upgrading if:
  • RAM consistently above 85%
  • CPU regularly maxed
  • TPS drops despite optimization
  • Player count outgrows plan

Still Having Issues?

Contact Support

Provide:
  • Current plan (RAM, etc.)
  • Average player count
  • List of mods/plugins
  • Spark/Timings report
  • When issues started
  • Discord
  • Support Ticket