Tune a Rust server for better performance

Rust performance comes down to how many entities your server is simulating, so the real wins are a sensible map size, working decay, fewer expensive plugins and a daily restart.

6 min read · Updated Oct 21, 2026 · By GuavaHost Team

Rust is one of the heaviest games you can host, and it gets heavier every day of a wipe. Knowing why makes tuning it much less of a guessing game.

What actually makes Rust heavy

Four things, roughly in order of how much they cost you.

Entity count. An entity is anything the server has to track: every foundation, wall, door, box, sleeping bag, deployable and dropped item. A single large clan base can be tens of thousands of entities on its own. Three weeks into a wipe your server is simulating far more than it was on day one, which is why lag tends to arrive gradually rather than overnight.

Map size. server.worldsize sets how big the world is. A bigger map does not just add ground, it adds monuments, roads, foliage, NPC spawn points and space for many more bases. It costs you memory on boot and CPU for the rest of the wipe.

Population. Every connected player is network traffic, entity updates and more building. Rust also keeps sleeping players in the world, so your player count keeps costing you something after people log off.

Single thread speed. Rust's main simulation loop runs largely on one CPU core, so single core clock speed matters more than the number of cores, and more RAM will not fix a server that is CPU bound. Why single thread performance matters covers that.

Why a smaller map beats more RAM

This is the single most useful thing to understand. If your server is struggling, dropping server.worldsize from 4500 to 3500 usually does more than adding another 4 GB of memory, because it cuts the simulation work as well as the memory footprint. A smaller map also concentrates players, which most communities enjoy more than an empty one.

Pick your size for the population you actually have, not the one you hope for:

Changing the size or seed regenerates the world, which wipes everything built in it, so treat it as a wipe and take a backup first. Back up and restore a Rust server save covers that, and How much RAM does a Rust server need? has the memory side.

The convars worth changing

A convar (console variable) is a Rust setting. You can set these live in the Console tab and then run server.writecfg to make them stick, or put them in server.cfg. How to edit Rust convars explains both routes and where the file lives.

• server.worldsize : map size, as above. The biggest lever you have.
• server.maxplayers : cap it near your real peak. A cap of 200 on a server that peaks at 40 just invites more building and more entities.
• server.saveinterval : how often, in seconds, the world is written to disk. The default of 600 is fine for most servers. Saving causes a brief hitch, so a longer interval means fewer hitches but more progress lost if the server dies. Do not push it past about 900 on a busy server.
• server.tickrate : how many times a second the server updates players. The default of 10 is what Facepunch tunes for. Raising it makes combat feel crisper and costs real CPU, so only try it if you have headroom, and step up gradually.
• decay.scale : the decay rate multiplier. 1 is normal. Turning decay off with 0 feels generous for a week and then buries your server in abandoned bases nobody will ever come back to. Leaving decay on is a performance setting, not just a gameplay one.
• decay.upkeep : whether tool cupboard upkeep applies. Same logic: upkeep is what removes dead clans' bases for you.
• spawn.max_density and spawn.max_rate : how densely the world spawns loot and resource nodes. Trimming these slightly helps a crowded map, but go gently, because players notice thin resources fast.
• ai.npc_enable : set to false to switch off scientist NPCs. It is a meaningful saving on a struggling server and a noticeable loss of content, so it is a last resort rather than a first move.
• gc.buffer : how much memory Rust buffers before garbage collection (the engine reclaiming unused memory). Owners of larger servers often raise it from the default, which trades memory for fewer collection stutters. Change it in steps and watch your memory use.

Everything above is a trade. Change one setting, let it run through a normal busy evening, then judge it. Changing six at once tells you nothing.

Plugins cost more than people think

The number of plugins is not what matters. What matters is whether a plugin is doing expensive work on a hook that fires constantly, like every damage event or every server tick. One badly written plugin can cost you more than twenty tidy ones.

If you are on Carbon, use its built-in profiler during a busy hour and look at which plugins are burning time. Installing Rust plugins with Oxide or Carbon walks through that, and The admin plugins most Rust servers run covers which ones are worth the cost in the first place.

Be especially careful with anything that scans the whole map on a timer, draws things for admins constantly, or logs every event to disk.

Scheduled restarts

Rust's memory use creeps up over days of uptime. A restart at a quiet hour clears it before anyone notices, and it is the cheapest performance fix on this page.

1. Open your server at customer.guavahost.com, then open Scheduled tasks in the server menu.
2. Use the Warn players, then restart starter if you want a chat warning first, or Restart every night for a plain one.
3. Pick a genuinely quiet hour for your players, not for you.

Setting up an automatic daily restart has the full walkthrough, including building the warning steps yourself.

Once a day suits almost every server. Twice is worth it only on big, heavily modded ones.

Work out what is actually wrong first

Server lag affects everyone at once and shows up as rubber-banding and delayed hits. A ping problem affects one player. Why is my server lagging? and Lag vs ping help you tell them apart before you change settings.

Then watch the Usage card on the Overview tab and Usage history over a few days. Memory pinned near your limit is a sizing problem. Memory fine but the server still stuttering under load is CPU, which points you at map size, entity count and plugins.

Common questions

What is the best world size for a Rust server?

For most communities, somewhere between 3500 and 4000 is the sweet spot: enough room for monuments and bases without spreading a modest population too thin. Go smaller if your peak is under about 30 players, and only go above 4500 if the server is genuinely busy and the hardware has room.

Will more RAM fix Rust lag?

Only if you are actually running out of memory. Rust's simulation runs mostly on a single CPU core, so if memory use is comfortable and the server still stutters when players are on, the fix is fewer entities, a smaller map or cheaper plugins rather than more RAM.

Does turning off decay help performance?

No, it hurts it. With decay off, bases from players who quit never disappear, so your entity count only ever goes up and the server gets slower every day of the wipe. Leaving decay and upkeep on is what keeps the map clean for you.

How often should a Rust server restart?

Once a day at a quiet hour is right for most servers, which is enough to clear the memory creep that builds up over a long uptime. Very large or heavily modded servers sometimes run two, but more than that is usually a sign something else needs fixing.

Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.

• rust
• performance
• convars
• worldsize
• decay

Host a Rust server From $15.99/mo, with instant setup and DDoS protection.

Still need help? Our team is online 24/7 to answer questions.

Contact support