How much memory does a Rust server need?
Realistic memory, disk and CPU needs for a Rust server on Schokr's free package, and how to keep it stable with a small map.
Updated · 2 min read
Rust needs a lot of memory. A small map with few players can fit in Schokr's free 6 GB pool if Rust is your only server, but large maps, many players or lots of plugins need more. World size is the biggest factor you control.
What drives Rust's memory use
- World size: bigger maps hold more terrain, monuments and entities in memory.
- Entities: every building block, deployable and dropped item adds up. Memory grows over a wipe as players build.
- Players: each connected player adds load.
- Plugins: Oxide itself and each plugin use memory.
Because memory grows over time, a server that boots fine on wipe day can run out of memory days later.
What fits in the free package
The free package gives your team one shared pool: 6 GB memory, 1.5 CPU cores, 10 GB disk, split across up to 4 servers.
| Setup | Free pool? |
|---|---|
| World size 1000 to 2000, a few friends, few plugins | Usually workable if Rust has most of the pool |
| World size 3000, 20 or more players | Tight; expect to need more memory |
| World size 3500 to 4500, busy public server | Needs well beyond 6 GB |
These are rough guides. Watch your own server's usage in the console.
Disk space
The Rust dedicated server files take several gigabytes on their own, and map files, saves, save backups and logs add more. On a 10 GB pool, give Rust most of the disk and avoid running another large server alongside it. Old .sav backups can be removed after a wipe.
Signs you're out of memory
- The server stops suddenly with no error, especially while generating a map or during a save.
- The console shows the server being killed or restarting unexpectedly.
- Memory usage in the console sits at the limit before the crash.
How to make it fit
- Lower the world size. This has the biggest effect. Changing it creates a new map, so do it at wipe time.
- Lower max players to what you actually need.
- Wipe more often. Fewer entities means less memory.
- Trim plugins. Remove anything you don't use.
- Give Rust more of your pool. If you run other servers, shrink or stop them.
- Add resources. The store sells permanent upgrades added to your team's pool: 1 GB memory for 450 credits, 50% CPU for 300 credits and 10 GB disk for 450 credits.
CPU and saves
Rust saves the world periodically, and saving causes a short freeze that grows with map size and entity count. If saves cause noticeable lag, a smaller map helps. You can adjust how often it saves with server.saveinterval in seconds, but saving less often means more progress lost if the server crashes.
Still stuck?
If you can't tell whether crashes are memory-related, share your console log and memory graph in the Schokr Discord.