Guides · 2 min read

Rust server optimisation: wipes, server FPS and plugins

How to keep server FPS high for the whole wipe, how to set up automatic wipes and what to watch out for when choosing Oxide and Carbon plugins.

The Noveric team
Noveric.cc

Rust is one of the most demanding games to host. Over a wipe the map fills with buildings, entities and players, and server FPS gradually drops. How do you keep it under control?

Server FPS – the key metric

A Rust server runs in a loop like other games. Server FPS tells you how many times per second the server can compute the world. When it drops too low, players feel desync, rubber-banding and delayed reactions.

What affects server FPS most:

  • Entity count – buildings, furniture, deployables, dropped items.
  • Map size – a bigger map means more monuments, NPCs and entities.
  • Plugins – one badly written plugin can slow the server more than a hundred players.
  • Single-core CPU performance – that’s why we build on the Ryzen 9 7950X3D.

Map size by player count

Players Recommended size (worldsize)
up to 50 2500–3000
50–150 3000–3500
150–300 3500–4250

Wipes

On the first Thursday of every month an update ships and a force wipe happens – every server must wipe the map. In between, you plan your own wipes (weekly, bi-weekly…).

Our control panel includes a wipe scheduler:

  • map wipes and BP wipes with configurable frequency,
  • automatic seed and map size rotation,
  • automatic server and Oxide/Carbon updates on force wipe day,
  • a backup before every wipe.

Oxide vs. Carbon

  • Oxide (uMod) – the most widespread framework with a huge plugin library.
  • Carbon – a more modern, performance-focused framework compatible with most Oxide plugins.

Both install in one click with us, and you can switch between them.

Tips for higher performance

  1. Limit entities – plugins to cap buildings and deployables per player.
  2. Watch decay – sensible decay removes abandoned bases.
  3. Test plugins – deploy a new plugin to a test server first.
  4. Restart regularly – a daily restart at the quietest time frees memory. Set it up in the scheduler.
  5. Watch memory – a Rust server gradually uses more RAM over a wipe. For community servers we recommend 12–16 GB.

Ready for wipe day

Wipe day is the biggest load of all – dozens of players join at the same moment. A powerful CPU and attack protection (wipe day is a popular time for DDoS) are essential. Check out Rust hosting.


#rust#oxide#carbon#wipe#performance

You might also like

Your server can be live in minutes.

Pick a game, choose a plan and leave the rest to us. Performance, protection and the control panel are all included.