How to Optimize Your Palworld Server for High Player Counts

Palworld dedicated servers can be incredibly demanding on hardware, especially as players explore the map, build massive bases, and capture hundreds of Pals. Managing server memory (RAM) is the key to a smooth experience.

1. The Memory Leak Problem

Currently, Palworld servers suffer from memory leaks over time. A server starting at 4GB of RAM usage can easily balloon to 16GB or 32GB after 24 hours of uptime with active players. When the server runs out of RAM, it crashes or begins to rubberband severely.

2. Scheduled Restarts are Mandatory

The only effective way to combat memory leaks is through scheduled restarts. Using the GameSphere task scheduler, set your Palworld server to restart every 6 to 12 hours depending on your player count.

3. Tweaking PalWorldSettings.ini

You can adjust specific settings to reduce the load on the server CPU and RAM. Open your PalWorldSettings.ini via the control panel:

• DropItemMaxNum=3000 - Lower this value (default is often higher) to reduce the number of dropped items that the server must track on the ground.
• PalSpawnNumRate=0.8 - Slightly reducing the global spawn rate of wild Pals can significantly reduce CPU calculations.
• AutoResetGuildNoOnlinePlayers=true and AutoResetGuildTimeNoOnlinePlayers=72.000000 - These settings automatically clean up abandoned bases after 72 hours of a guild being offline, freeing up massive amounts of memory.

4. Choose the Right Hosting Plan

Because of these memory demands, we strongly recommend a plan with at least 16GB of RAM for a public Palworld server. GameSphere's automated monitoring will also alert you if your RAM usage approaches the limit.