Optimize performance and reduce lag

A Rust server degrades when too many entities, buildings and events pile up. The tick rate drops, players “teleport” and raids get unstable. A few settings in server.cfg are usually enough to recover a smooth server.

Cause / The problem

Rust lag generally comes from three sources: a server.maxplayers set too high for the allocated RAM, a too-frequent save that freezes the main thread, and insufficient decay that lets hundreds of abandoned bases accumulate.

Solution

1. Match server.maxplayers to your RAM. Rule of thumb: about 1 GB per 20-25 active players; above that, upgrade in the panel. Do not set 200 slots if your machine can hold 80.
2. Raise server.saveinterval responsibly. The default is 300 seconds:

   server.saveinterval 600

   Each save briefly freezes the server; moving to 600 s reduces micro-stutters, but never go below 300 s or you risk data loss on a crash.
3. Enable more aggressive decay to clean up abandoned bases:

   decay.scale 1
   decay.tick 300

   A decay.scale of 1 (default) or slightly higher speeds up the rot of unmaintained buildings.
4. Disable unused convars depending on your style (PvE, noob-friendly):

   server.pve true
   heli.enabled false
   bradley.enabled false

5. Schedule a daily restart in the panel (Schedules → restart at 4 AM). A reboot frees memory and prevents leaks on long sessions.
6. Keep the server up to date: install Facepunch updates as soon as they land (Steam Workshop tab / validate game files) — an outdated version causes disconnects and desync.
7. Limit CPU-hungry uMod plugins: some (economy, tracking) are heavy. Disable them one by one to identify the culprit behind sudden lag.

Monitor the tick with perf.report in the console: a healthy server stays above 30 server FPS.