How to Optimize Minecraft Server Performance

Complete guide to maximize your Minecraft server's TPS, reduce lag, and improve player experience with JVM tuning and configuration optimization.

Published: March 5, 2026 | Author: NGP Hosts Team | Tags: optimization performance tuning | Reading time: 10 minutes

Introduction

Minecraft server performance directly impacts player experience through TPS (Ticks Per Second), lag, and response times. Optimizing your server can transform a laggy experience into smooth gameplay even with dozens of players. This comprehensive guide covers JVM tuning, server configuration, plugin optimization, and hardware considerations for maximum performance.

Understanding Server Performance Metrics

TPS (Ticks Per Second)

TPS measures how many game updates occur per second. Ideal TPS is 20.0:

  • 20 TPS: Perfect performance
  • 15-19 TPS: Minor lag, acceptable
  • 10-14 TPS: Noticeable lag
  • 5-9 TPS: Severe lag
  • <5 TPS: Unplayable

Memory Usage

Monitor RAM allocation and garbage collection:

/tps - Check current TPS
/memory - View memory usage
/gc - Manually trigger garbage collection

JVM Optimization

Essential JVM Flags

These JVM arguments provide optimal performance for most servers:

-Xms4G -Xmx4G
-XX:+UseG1GC
-XX:+ParallelRefProcEnabled
-XX:MaxGCPauseMillis=200
-XX:+UnlockExperimentalVMOptions
-XX:+DisableExplicitGC
-XX:+AlwaysPreTouch
-XX:G1NewSizePercent=30
-XX:G1MaxNewSizePercent=40
-XX:G1HeapRegionSize=8M
-XX:G1ReservePercent=20
-XX:G1HeapWastePercent=5
-XX:G1MixedGCCountTarget=4
-XX:InitiatingHeapOccupancyPercent=15
-XX:G1MixedGCLiveThresholdPercent=90
-XX:G1RSetUpdatingPauseTimePercent=5
-XX:SurvivorRatio=32
-XX:+PerfDisableSharedMem
-XX:MaxTenuringThreshold=1
-Dusing.aikars.flags=https://mcflags.emc.gs
-Daikars.new.flags=true

Memory Allocation Guidelines

Allocate memory based on player count and world size:

  • 1-5 players: 2GB RAM (Xms2G -Xmx2G)
  • 5-10 players: 4GB RAM (Xms4G -Xmx4G)
  • 10-20 players: 6GB RAM (Xms6G -Xmx6G)
  • 20-50 players: 8GB RAM (Xms8G -Xmx8G)
  • 50+ players: 12GB+ RAM

Alternative JVM Configurations

For Low-End Servers (2GB RAM):

-Xms1G -Xmx2G
-XX:+UseG1GC
-XX:+UseStringDeduplication
-XX:+OptimizeStringConcat
-XX:+UseCompressedOops
-XX:+UseCompressedClassPointers

For High-End Servers (16GB+ RAM):

-Xms12G -Xmx16G
-XX:+UseG1GC
-XX:G1HeapRegionSize=16M
-XX:+UseLargePages
-XX:+UseTransparentHugePages
-XX:+AggressiveOpts

Server Properties Optimization

Performance-Critical Settings

Edit your server.properties file for optimal performance:

# Reduce view distance (default 10)
view-distance=6

# Limit simulation distance (1.18+)
simulation-distance=4

# Optimize entity activation
entity-broadcast-range-percentage=80

# Reduce network timeout
network-timeout=30

# Optimize chunk loading
max-chained-neighbor-updates=500

# Limit mob spawning
mob-spawning-range=6

# Optimize world saving
max-tick-time=60000

# Enable optimization for single-threaded servers
enable-jmx-monitoring=false

Advanced Configuration

# Reduce chunk generation delay
max-chained-neighbor-updates=500

# Optimize entity processing
entity-tracking-range=64

# Limit item despawn time
item-despawn-rate=6000

# Optimize redstone
max-redstone-signal-distance=32

# Reduce world border size if not needed
world-border-size=29999984

Plugin Optimization

Essential Performance Plugins

ClearLagg

Automatically removes entities to prevent lag:

/lagg clear - Remove entities
/lagg chunk - Unload chunks
/lagg gc - Force garbage collection

Spark

Advanced profiling tool to identify lag sources:

/spark profiler start - Begin profiling
/spark profiler stop --timeout 60 - Stop after 60 seconds
/spark profiler --last - View last profile

Plugin Management Best Practices

  • Remove unused plugins regularly
  • Keep plugins updated to latest versions
  • Avoid duplicate functionality plugins
  • Configure plugins to reduce database queries
  • Use lightweight alternatives when possible

Database Optimization

For plugins using databases (CoreProtect, LuckPerms):

  • Use MySQL instead of SQLite for high traffic
  • Configure connection pooling
  • Set appropriate cache sizes
  • Regular database maintenance
  • Consider Redis for caching

World and Chunk Optimization

Pre-Generation

Generate chunks in advance to prevent lag:

# Using WorldBorder
/worldborder set 5000
/worldborder center 0 0
/worldborder damage amount 0

# Using Chunky plugin
/chunky radius 5000
/chunky start

World Management

  • Use separate worlds for different purposes
  • Reset resource worlds regularly
  • Limit world size with WorldBorder
  • Use Multiverse for world management
  • Archive old worlds instead of deleting

Chunk Optimization

# Optimize chunk loading
chunk-gc-period-in-ticks=600

# Reduce chunk sending distance
no-view-chunking=true

# Optimize chunk caching
chunk-send-distance=6

Network Optimization

Network Settings

# Optimize network compression
network-compression-threshold=256

# Reduce packet size
packet-compression=2

# Optimize connection handling
online-mode=true

# Set appropriate timeout
network-timeout=30

Proxy Configuration

For servers with high player counts, consider BungeeCord/Velocity:

  • Distribute players across multiple servers
  • Reduce individual server load
  • Enable cross-server communication
  • Optimize network routing

Hardware and System Optimization

CPU Considerations

  • Single-threaded performance: Minecraft benefits from high clock speeds
  • Core count: 4+ cores recommended for busy servers
  • Architecture: x86_64 with SSE4.2 support
  • CPU governor: Set to performance mode

Storage Optimization

  • SSD preferred: Dramatically improves world loading
  • NVMe SSD: Best for large servers
  • RAID configuration: RAID 1 for reliability, RAID 0 for speed
  • File system: ext4 with noatime option

Operating System Tuning

# Set CPU governor to performance
echo performance | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

# Optimize network settings
echo 'net.core.rmem_max = 26214400' | sudo tee -a /etc/sysctl.conf
echo 'net.core.wmem_max = 26214400' | sudo tee -a /etc/sysctl.conf

# Apply changes
sudo sysctl -p

Monitoring and Maintenance

Performance Monitoring Tools

# Built-in commands
/tps - Check server TPS
/lag - View lag information
/memory - Monitor memory usage
/timings - Generate performance report

# External tools
htop - System resource monitor
iotop - Disk I/O monitor
nethogs - Network usage monitor

Regular Maintenance Tasks

  • Daily: Check TPS and memory usage
  • Weekly: Review plugin performance
  • Monthly: Clean up old logs and data
  • Quarterly: Update all plugins and server version

Backup Strategy

# Automated backup script
#!/bin/bash
DATE=$(date +%Y%m%d_%H%M%S)
tar -czf backup_$DATE.tar.gz world/
find /path/to/backups/ -name "*.tar.gz" -mtime +7 -delete

Troubleshooting Common Issues

Low TPS Issues

  • Check with /spark profiler to identify lag sources
  • Reduce view distance in server.properties
  • Remove or optimize resource-intensive plugins
  • Check for entity buildup with /lagg entities
  • Consider world reset if corruption suspected

Memory Issues

  • Increase heap size with -Xmx flag
  • Check for memory leaks with profiling tools
  • Optimize JVM garbage collection settings
  • Reduce player count or world size
  • Consider upgrading server hardware

Network Lag

  • Check server internet connection speed
  • Optimize network compression settings
  • Reduce view distance and simulation distance
  • Use proxy for load distribution
  • Check for DDoS attacks

Advanced Optimization Techniques

Custom JVM Arguments

For specific use cases:

# For modded servers
-XX:+UseConcMarkSweepGC
-XX:+CMSIncrementalMode
-XX:-UseAdaptiveSizePolicy

# For minigame servers
-XX:+UseG1GC
-XX:MaxGCPauseMillis=50
-XX:G1HeapRegionSize=4M

Container Optimization

If running in Docker:

# Docker compose example
services:
  minecraft:
    image: openjdk:17
    environment:
      - JAVA_OPTS="-Xms4G -Xmx4G -XX:+UseG1GC"
    ulimits:
      nofile:
        soft: 65536
        hard: 65536

Conclusion

Optimizing a Minecraft server is an ongoing process that requires monitoring, adjustment, and maintenance. Start with the essential JVM flags and server.properties optimizations, then gradually implement advanced techniques based on your server's specific needs. Regular monitoring and maintenance ensure consistent performance as your server grows.

Remember that every server is unique - what works for a small survival server may not suit a large minigame network. Test changes incrementally and always keep backups before major optimizations.

Need better hosting for your optimized server? Try NGP Hosts - Scale from 4GB to 64GB RAM with community rewards!

Related Articles