# Palworld Server Performance Optimization (/docs/palworld/optimize-performance)



import { Step, Steps } from 'fumadocs-ui/components/steps';

Palworld servers have known memory leak issues. Here's how to keep things running smoothly.

Key Settings to Tune [#key-settings-to-tune]

In `Pal/Saved/Config/LinuxServer/PalWorldSettings.ini`:

| Setting                           | Default | Recommended           | Impact                                                 |
| --------------------------------- | ------- | --------------------- | ------------------------------------------------------ |
| `BaseCampWorkerMaxNum`            | `15`    | `10–15`               | **Biggest lever** — each worker runs AI                |
| `DropItemMaxNum`                  | `3000`  | `2000`                | Fewer dropped items in world                           |
| `DropItemAliveMaxHours`           | `1.0`   | `0.5`                 | Faster cleanup of dropped items                        |
| `PalSpawnNumRate`                 | `1.0`   | `0.8–1.0`             | Fewer Pals = less CPU                                  |
| `MaxBuildingLimitNum`             | `0`     | `5000–10000`          | Prevents structure bloat (0 = unlimited)               |
| `ServerReplicatePawnCullDistance` | `15000` | `8000–10000`          | Pal sync range — lower = less network                  |
| `bEnableInvaderEnemy`             | `True`  | `False` if RAM issues | Raids contribute significantly to memory leaks         |
| `AutoSaveSpan`                    | `15.0`  | `30.0–60.0`           | Seconds between auto-saves — higher reduces I/O spikes |

RAM Requirements [#ram-requirements]

| Players | Minimum | Recommended |
| ------- | ------- | ----------- |
| 1–8     | 8 GB    | 12 GB       |
| 8–16    | 12 GB   | 16 GB       |
| 16–32   | 16 GB   | 32 GB       |

Schedule Regular Restarts [#schedule-regular-restarts]

The server has a known memory leak. Schedule restarts every **4–6 hours** to clear accumulated memory (every **1 hour** if you keep `bEnableInvaderEnemy=True`).

In the [XGamingServer Panel](https://panel.xgamingserver.com), click **Schedules** in the sidebar to set up automatic restarts.

> For the full memory leak playbook (the three-fix combo that actually solves it), see [Memory Leak Fix](/docs/palworld/memory-leak-fix).

Performance Monitoring [#performance-monitoring]

Use the REST API to check server health:

```bash
curl -u admin:password http://localhost:8212/v1/api/metrics
```

**Target values:**

* Server FPS: **60+** (good), below 50 is poor
* RAM under 8 GB is healthy, over 12 GB is concerning

Engine.ini Optimizations [#engineini-optimizations]

Create or edit `Engine.ini` in the same config folder as `PalWorldSettings.ini`:

```ini
[/Script/OnlineSubsystemUtils.IpNetDriver]
NetServerMaxTickRate=120

[/Script/Engine.GarbageCollectionSettings]
gc.TimeBetweenPurgingPendingKillObjects=60
```

General Tips [#general-tips]

* **Disable raids** (`bEnableInvaderEnemy=False`) if experiencing RAM issues — this is a major contributor
* Use **SSD storage** for save files
* Linux servers run more efficiently than Windows on long uptimes
* Reduce `BaseCampWorkerMaxNum` before reducing `PalSpawnNumRate` — worker AI is more expensive than wild Pal spawns

Related Guides [#related-guides]

* [Memory Leak Fix](/docs/palworld/memory-leak-fix)
* [Server Configuration](/docs/palworld/server-settings)
* [Player Count](/docs/palworld/player-count)
* [REST API](/docs/palworld/rest-api)
* [Backup & Restore](/docs/palworld/backup-restore)