Selecting an oversized map on an entry-level VPS frequently leads to boot-time generation crashes or severe lag a few days into a wipe. Rust dedicated server memory usage depends not only on player count, but fundamentally on procedural map area and entity accumulation over time.
This guide targets Linux Rust administrators sizing server instances. As of October 27, 2026, procedural world size (server.worldsize) is defined in meters, where the standard 4500-meter default requires significantly more RAM than compact 3000–3500-meter maps.
How world size impacts memory allocation#
The +server.worldsize parameter specifies the edge length of the square game world. Total world area increases quadratically, directly scaling memory demands:
worldsize | Map area | Baseline boot RAM | Recommended VPS RAM | Typical format |
|---|---|---|---|---|
2500–3000 | 6.25–9.0 km² | ~5–7 GB | 8–10 GB | Solo / Duo / Trio, high-action PvP |
3250–3750 | 10.5–14.0 km² | ~8–10 GB | 12–16 GB | Medium communities (up to 70 players) |
4000–4500 | 16.0–20.25 km² | ~11–14 GB | 16–24 GB | Standard Vanilla (100–200 players) |
5000+ | 25.0+ km² | ~15–18+ GB | 24–32 GB | Large clan / massive community worlds |
A 4500-meter map covers 20.25 km²—more than double the surface area of a 3000-meter map (9 km²). The engine must allocate RAM for significantly more foliage, rock colliders, monuments, roadways, and AI navigation nodes.
Navmesh generation memory spikes#
The most vulnerable point in a server's lifecycle occurs during initial procedural generation and AI navigation mesh (Navmesh) calculation.
With nav_disable set to false (the default), the server bakes navigation data for animals and scientists across the entire terrain. On 4500+ maps, this baking process produces a temporary 3–5 GB memory spike. If total host memory is constrained, the Linux kernel triggers the Out of Memory (OOM) Killer, terminating the process with Killed.
Check available memory and kernel OOM records with standard tools:
free -h
sudo dmesg -T | grep -i -E 'oom[-_]killer|killed process'
For hosts with limited memory (8–12 GB), lowering worldsize to 3250–3500 meters is far safer than attempting to disable navmesh, as disabling navigation breaks NPC mechanics.
Entity accumulation during the wipe cycle#
An empty, freshly wiped Rust world consumes minimal baseline memory. As players erect multi-story bases, deploy automated turrets, place storage boxes, and scatter sleeping bags, the total entity count rises continuously.
Every 50,000 additional entities add roughly 1.5–2.5 GB to active resident memory. Inspect current entity numbers from the server console:
save
entity.count
If entity counts exceed 200,000 midway through a wipe cycle, a 4500-meter world requires at least 16–18 GB of RAM. Running on an 8 GB or 10 GB VPS guarantees out-of-memory termination as weekend player activity peaks.
Setting map size in startup scripts#
Configure your target map size and seed directly in the startup command:
./RustDedicated -batchmode \
+server.port 28015 \
+server.worldsize 3500 \
+server.seed 148290 \
+server.maxplayers 75
Provision a 4–8 GB swap file on fast NVMe storage. Swap cannot substitute for fast physical RAM during active gameplay, but it prevents sudden kernel process termination during boot-time generation spikes.
If you orchestrate your game nodes using Nexardo, align virtual machine allocations with the physical dimensions of your chosen world: adequate RAM headroom prevents unexpected server restarts during peak hours.
