Skip to main content

Palworld Server Optimization

This guide provides comprehensive optimization strategies for your Palworld dedicated server to ensure smooth gameplay, minimal lag, and optimal performance for all players.

Performance Baseline

Before optimizing, understand your server’s current performance:
Monitor these metrics through your Wasabi Hosting Gamepanel or in-game console commands.

Configuration Optimization

Core Settings Optimization

Optimize PalWorldSettings.ini for better performance:
BaseCampWorkerMaxNum has the most significant performance impact. Start at 10 and adjust based on player feedback.

Engine Configuration

Optimize Engine.ini for maximum performance:
Changing TickRate below 50 may negatively impact gameplay. 60 is optimal for most servers.

Startup Parameter Optimization

Configure these in your Wasabi Hosting Gamepanel:

Memory Optimization

Memory Management Settings

RAM Allocation Guidelines

These requirements include OS overhead and other background processes. Dedicated servers should have 20-30% RAM headroom.

CPU Optimization

Multi-Threading Configuration

CPU Affinity and Priority

On Windows servers, configure CPU affinity:
Set the Palworld server process priority to “High” in Task Manager for better CPU allocation.

Network Optimization

Network Configuration

Bandwidth Optimization

These values are for upload bandwidth, which is typically the limiting factor for game servers.

Entity and World Optimization

Item Management

Setting DropItemMaxNum too low may cause items to disappear during intense gameplay. 2000-2500 is a good balance.

Pal Spawn Optimization

Base and Building Optimization

BaseCampWorkerMaxNum directly impacts performance. Each worker Pal actively calculates pathfinding and tasks.

Database and Save Optimization

Save Game Settings

Automatic Backups

Configure automatic saves and backups:
  • In Wasabi Gamepanel: Set up automated backups every 6-12 hours
  • Manual saves: Use /Save command regularly via RCON
  • Backup rotation: Keep 3-7 days of backups
Regular saves prevent data loss but cause brief performance dips. Schedule during low-traffic periods.

Performance Scaling by Player Count

Small Server (1-8 Players)

Medium Server (8-16 Players)

Large Server (16-32 Players)

Monitoring and Diagnostics

Performance Monitoring

Use RCON commands to monitor performance:

Log Analysis

Monitor logs for performance issues:
Set up log rotation to prevent log files from consuming too much disk space.

Platform-Specific Optimizations

Windows Server

Linux Server

Advanced Optimization Techniques

Memory Pooling

Async Loading

Garbage Collection Optimization

Anti-Lag Measures

Entity Cleanup Scripts

Create automated cleanup via RCON:

Dynamic Performance Adjustment

Monitor and adjust settings based on load:

Hardware Recommendations

For 1-8 Players:
  • CPU: 4 cores @ 3.5GHz+
  • RAM: 12 GB
  • Storage: 50 GB SSD
  • Network: 25 Mbps
For 8-16 Players:
  • CPU: 6 cores @ 4.0GHz+
  • RAM: 16 GB
  • Storage: 100 GB SSD
  • Network: 50 Mbps
For 16-24 Players:
  • CPU: 8 cores @ 4.5GHz+
  • RAM: 24 GB
  • Storage: 150 GB NVMe SSD
  • Network: 100 Mbps
For 24-32 Players:
  • CPU: 12 cores @ 5.0GHz+
  • RAM: 32 GB
  • Storage: 200 GB NVMe SSD
  • Network: 200 Mbps
SSD/NVMe storage is crucial for fast world saves and loads. HDD significantly impacts performance.

Optimization Checklist

Use this checklist to optimize your server:
  • Set appropriate player limit for hardware
  • Reduce BaseCampWorkerMaxNum to 8-12
  • Configure DropItemMaxNum to 2000-2500
  • Enable faster item cleanup (0.5 hours)
  • Set NetServerMaxTickRate to 60
  • Enable multithreading startup parameters
  • Configure automatic backups
  • Set process priority to High
  • Enable garbage collection optimization
  • Configure log rotation
  • Optimize network settings
  • Enable RCON for monitoring
  • Set up automated saves
  • Monitor RAM usage regularly
  • Review and update configuration monthly

Troubleshooting Performance Issues

Common Causes:
  • Too many players for hardware
  • High BaseCampWorkerMaxNum
  • CPU bottleneck
  • Too many active bases
Solutions:
  • Reduce ServerPlayerMaxNum
  • Lower BaseCampWorkerMaxNum to 8-10
  • Reduce PalSpawnNumRate to 0.8
  • Increase cleanup frequency
  • Upgrade CPU or reduce player count
Common Causes:
  • Memory leaks
  • Too many entities
  • Large world size
  • Insufficient cleanup
Solutions:
  • Enable aggressive item cleanup
  • Reduce DropItemMaxNum
  • Restart server daily
  • Enable garbage collection optimization
  • Reduce BaseCampMaxNum if possible
Common Causes:
  • Insufficient bandwidth
  • Network congestion
  • DDoS attack
  • Poor routing
Solutions:
  • Upgrade network bandwidth
  • Enable DDoS protection (Firewall Manager)
  • Reduce MaxClientRate if needed
  • Limit ServerPlayerMaxNum
  • Check for background network processes
Common Causes:
  • Slow storage (HDD vs SSD)
  • Large world size
  • Many players/bases
  • Fragmented files
Solutions:
  • Upgrade to SSD or NVMe storage
  • Regular world cleanup
  • Optimize save intervals
  • Defragment storage (if HDD)
  • Enable backup compression
Common Causes:
  • Out of memory
  • Corrupted save files
  • Mod conflicts
  • Hardware issues
Solutions:
  • Increase allocated RAM
  • Restore from backup
  • Remove problematic mods
  • Check hardware health
  • Update server software
  • Review crash logs

Maintenance Schedule

Regular maintenance ensures optimal performance:

Daily Tasks

  • Monitor server performance metrics
  • Check player count vs. performance
  • Verify no error messages in logs
  • Quick backup verification

Weekly Tasks

  • Full server restart
  • Log file cleanup and review
  • Performance benchmark
  • Backup rotation verification
  • Check for updates

Monthly Tasks

  • Deep performance analysis
  • Configuration optimization review
  • Hardware health check
  • Storage cleanup
  • Update all software
  • Review player feedback
Schedule maintenance during off-peak hours (early morning) to minimize player disruption.

Performance Testing

Stress Testing

Test server performance under load:
1

Establish baseline

Record metrics with normal player count
2

Simulate high load

Test with maximum expected players
3

Monitor metrics

Track FPS, RAM, CPU, network during test
4

Identify bottlenecks

Find performance limiting factors
5

Adjust and retest

Optimize and test again

Benchmark Commands

Final Optimization Tips

Key Optimization Principles:
  • Start conservative: Begin with lower limits and increase gradually
  • Monitor constantly: Regular performance checks prevent issues
  • One change at a time: Test each optimization individually
  • Document changes: Keep records of what works
  • Player feedback: Listen to player reports of lag
  • Regular restarts: Daily restarts prevent memory leaks
  • Update regularly: Keep server software current
  • Backup everything: Always backup before major changes
By following this comprehensive optimization guide, your Palworld server on Wasabi Hosting will deliver excellent performance and a smooth, enjoyable experience for all players. For additional assistance, contact our support team.

Get your own Palworld server

Deploy a DDoS-protected Palworld server on AMD Ryzen hardware in about two minutes. Plans start at €9.00/month.