Skip to content

Server Performance

Server performance affects every aspect of your game server experience. Poor performance leads to lag, crashes, and frustrated players. This guide helps you identify, diagnose, and resolve performance issues.

📊 Check Platform Status: Before troubleshooting individual server performance, check status.gamelords.gg to see if there are any infrastructure issues affecting performance across our platform.

  • Target: 20+ FPS minimum, 60+ FPS ideal
  • Impact: Low FPS causes stuttering and input lag
  • Monitoring: Check console or control panel graphs
  • Target: Below 80% average usage
  • Impact: High CPU causes lag spikes and instability
  • Monitoring: Resource graphs in control panel
  • Target: Below 90% of allocated RAM
  • Impact: High memory usage leads to crashes
  • Monitoring: Real-time memory graphs
  • Bandwidth: Monitor incoming/outgoing traffic
  • Latency: Player ping times
  • Packet Loss: Should be near 0%

Most games provide performance commands:

// Source Engine games (CS2, TF2, GMod, L4D2)
net_graph 3 # Network performance overlay
developer 1 # Enable developer console
host_speeds 1 # Show frame timing
// Minecraft
/tps # Server ticks per second
/lag # Memory and timing info
// Rust
perf 1 # Performance overlay
fps.graph 1 # FPS graph display

Your Game Lords control panel provides:

  • Real-time resource usage graphs
  • Historical performance data
  • Alert notifications for issues
  • Performance trend analysis
  • Game servers: Often limited by single-core performance
  • Background tasks: Can utilize multiple cores
  • Optimization focus: Reduce main thread workload

Common CPU bottlenecks:

  • Complex AI calculations
  • Physics simulations
  • Plugin/mod processing
  • Player input handling
  • World generation/loading

Minecraft:

# Reduce entity processing
entity-activation-range.animals=16
entity-activation-range.monsters=24
entity-activation-range.raiders=48
entity-activation-range.misc=8
# Optimize world generation
chunk-gc-period-in-ticks=600
max-auto-save-chunks-per-tick=6
max-tick-time=60000

Rust:

# Reduce AI processing
ai.think 1
ai.move 1
ai.sensetime 1
# Optimize spawn rates
spawn.max_rate 1
spawn.max_density 1

ARK:

# Reduce wild dino processing
DinoCountMultiplier=0.8
NPCReplacements to remove high-CPU creatures
  1. Audit installed plugins: Remove unnecessary ones
  2. Update regularly: Newer versions often perform better
  3. Profile performance: Identify resource-heavy plugins
  4. Alternative solutions: Find lighter alternatives
  • Smaller worlds: Reduce map size if possible
  • Entity cleanup: Regular removal of unused entities
  • Chunk management: Optimize world loading patterns
  • Pregeneration: Generate worlds during off-hours
  • Gradual increase: Normal as worlds grow
  • Stable during play: Should plateau during active gameplay
  • Cleanup on restart: Memory should reset after restart

Warning signs:

  • Continuously increasing memory usage
  • Performance degradation over time
  • Crashes after extended uptime
  • Unusual memory patterns in graphs
Terminal window
# Optimized JVM arguments
-Xmx4G -Xms4G
-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
# Memory optimization
sv_memory_pool_chunks 256
sv_memory_pool_maxsize 128
host_thread_mode 0
mat_queue_mode 2
  1. Regular restarts: Schedule during low-activity periods
  2. Cleanup scripts: Automate entity removal
  3. Backup management: Don’t store excessive backups on server
  4. Log rotation: Prevent log files from growing too large
  • SSD: 10-100x faster random access, ideal for servers
  • HDD: Slower but cheaper, acceptable for static content
  • NVMe: Fastest option, best for high-performance servers
  1. File organization: Keep active files on fast storage
  2. Cleanup routines: Remove old logs and temporary files
  3. Backup placement: Store backups on separate storage
  4. Database optimization: Maintain database files regularly
# Example optimizations by game
# Minecraft
save-user-cache-on-stop-only=true
autosave.period=6000
# Rust
server.saveinterval 600
server.official false
  • Sequential access: Organize files for sequential reading
  • Batch operations: Group file operations together
  • Cache frequently accessed data: Keep common files in memory
  • Avoid fragmentation: Regular disk maintenance
  • Upload speed: Server to players (usually the bottleneck)
  • Download speed: Players to server (less critical)
  • Burst capacity: Handle traffic spikes
  • Geographic distance: Physical distance affects ping
  • Network routing: Internet backbone routing efficiency
  • Server processing: Time to process requests
  • Client performance: Player hardware and connection

Source Engine Games:

# Optimize for 32 players
sv_maxrate 786432 # Max bandwidth per player
sv_minrate 196608 # Minimum bandwidth
sv_maxcmdrate 128 # Command rate (128 tick)
sv_maxupdaterate 128 # Update rate (128 tick)
rate 786432 # Default player rate

Minecraft:

# Network optimization
network-compression-threshold=256
netty-threads=4
  1. Player limits: Don’t exceed server capacity
  2. Rate limiting: Prevent bandwidth abuse
  3. Priority systems: Important data first
  4. Compression: Reduce data transmission

For games supporting fast downloads:

  1. Web server: Set up HTTP/HTTPS download server
  2. Compression: Use bzip2 or gzip compression
  3. CDN: Content delivery network for global reach
  4. Caching: Enable browser and proxy caching
  • Size limits: Restrict total mod size
  • Quality control: Only include necessary content
  • Update management: Coordinate mod updates
  • Alternative sources: Multiple download mirrors
  • Paper: Best performance for Bukkit plugins
  • Fabric: Lightweight for mods
  • Forge: Required for Forge mods but heavier
  • Vanilla: Lightest but limited functionality
# Paper configuration optimizations
world-settings:
default:
view-distance: 8
simulation-distance: 6
mob-spawn-range: 6
entity-activation-range:
animals: 16
monsters: 24
raiders: 48
misc: 8
water: 16
villagers: 16
flying-monsters: 32
# Performance-focused settings
fps.limit 30
server.tickrate 20
physics.steps 60
graphics.renderscale 1
ai.think 1
spawn.max_rate 1
spawn.max_density 1
  • Map size: Smaller maps = better performance
  • Seed selection: Some seeds perform better
  • Custom maps: Optimized maps available
  • Wipe frequency: Regular wipes improve performance
# Performance settings
LaunchParameters=-USEALLAVAILABLECORES -sm4 -lowmemory
bDisableStructurePlacementCollision=true
ResourceNoReplenishRadiusPlayers=1.0
ResourceNoReplenishRadiusStructures=1.0
  • Structure cleanup: Remove abandoned buildings
  • Dino cleanup: Limit wild dinosaur populations
  • Regular restarts: Prevent memory buildup
  • Save optimization: Use save compression
# FPS and performance
fps_max 300
host_thread_mode 0
mat_queue_mode 2
r_threaded_renderdata 1
# Network performance
sv_parallel_sendsound 1
sv_compressskeletondata 1
net_maxfilesize 64
  1. Enable alerts: Set thresholds for CPU, RAM, and disk
  2. Historical data: Review trends over time
  3. Real-time graphs: Monitor during peak hours
  4. Export data: Download performance reports
# Enable performance displays
net_graph 3 # Source Engine
/tps # Minecraft
perf 1 # Rust
stat fps # ARK
  1. Fresh server: Record performance after clean install
  2. Peak load: Monitor during maximum players
  3. Different times: Performance varies by time of day
  4. After changes: Always test after modifications
Game TypeTarget FPSMax CPU %Max RAM %
Minecraft20+80%85%
Rust20+75%90%
ARK30+80%85%
Source Games60+70%80%
  1. Identify symptoms: Lag, crashes, timeouts
  2. Check resources: CPU, RAM, disk, network
  3. Review recent changes: New plugins, settings, players
  4. Test minimal configuration: Disable all modifications
  5. Isolate the cause: Add components back gradually
  • Too many plugins/mods: Reduce to essentials only
  • Inefficient plugins: Replace with optimized alternatives
  • Oversized worlds: Consider world borders or cleanup
  • High player counts: Match players to server capacity
  • Memory leaks: Regular restarts or plugin fixes
  1. Reduce player count: Temporarily lower max players
  2. Restart server: Clear memory and reset processes
  3. Disable plugins: Remove non-essential modifications
  4. Check resources: Verify no external resource usage
  • Optimize settings: Reduce quality for stability
  • Schedule restarts: More frequent server restarts
  • Player communication: Inform players of limitations
  • Monitor closely: Watch for recurring issues
  • Server upgrade: More CPU, RAM, or better storage
  • Code optimization: Plugin updates or replacements
  • Architecture changes: Clustering or load balancing
  • Professional consultation: Expert performance analysis

When seeking performance help:

  1. Performance graphs: Screenshots from control panel
  2. Server configuration: Settings and modifications
  3. Player counts: Typical and peak concurrent players
  4. Recent changes: Any modifications before issues started
  5. Error logs: Console output showing problems

Game Lords offers advanced performance services:

  • Performance audits: Comprehensive server analysis
  • Custom optimization: Tailored configuration tuning
  • Monitoring setup: Advanced alerting and reporting
  • Emergency support: Priority assistance for critical issues

Remember: Performance optimization is an ongoing process. Regular monitoring and adjustment ensure your server continues to provide the best possible experience for your players.

Need Advanced Help? Performance issues can be complex and server-specific. If you’re experiencing persistent performance problems:

🎫 Submit a Performance Ticket: Visit help.gamelords.gg and include:

  • Performance graphs from your control panel
  • Server specifications and current player count
  • Mods/plugins installed
  • Recent changes made to the server
  • Specific times when issues occur

📞 Priority Support: Performance issues affecting gameplay get priority response. Our team can provide:

  • Remote server analysis
  • Custom optimization recommendations
  • Real-time monitoring setup
  • Emergency performance assistance

Professional Services Available:

  • Comprehensive performance audits
  • Custom optimization consulting
  • Advanced monitoring solutions
  • 24/7 priority support plans