Why Your Rust Server Is Lagging

Players say the server feels bad: rubber-banding, delayed hits, doors that take a second to open. Rust servers slow down for a small number of reasons, and the panel graphs the ones that matter, so you can find the cause rather than guessing.

1Look at the Graphs

• Log in to your game panel and click your Rust server.
• Click Players in the left menu, then the Performance tab.
• Choose 6 h, 24 h or 7 days. History is kept for 14 days, sampled every minute.

Four graphs, each with its peak for the period. The peak matters more than the current value: a server that was fine when you looked is not the one your players complained about.

2Server FPS

• This is the clearest signal. Under 30 feels laggy to players, and the graph labels it as such.
• Healthy is well above that. If FPS is fine and players still complain, the problem is more likely their connection than your server.
• FPS dropping at a predictable time of day usually means player count. FPS falling steadily over days usually means entities.

3Entities

• Entities are every base, deployable, dropped item and piece of loot in the world. The count only ever grows during a wipe cycle.
• It is the most common cause of a server that gets worse as the week goes on. It also slows saves, which is felt as a stutter every save interval.
• Around 300,000 is where to start paying attention. Around 500,000 you will feel it.

What to do about it:

• Wipe. A map wipe resets the count to nothing. This is why servers wipe weekly, not just for fairness. See how to wipe your Rust server.
• Lower the despawn timers. Item despawn and corpse despawn in Rust settings decide how long loose loot lingers.
• Leave decay on. Decay is what removes bases nobody maintains. Turning it off is a popular request and a slow way to fill your world with abandoned structures.

4Memory

• Memory climbing steadily across days is normal for Rust and is what a daily restart is for.
• If it climbs sharply after you installed something, suspect a plugin. Remove the newest one and watch the graph.
• See how to set up automatic restarts.

5Players Online

• Use this to line up the other three. FPS dropping exactly when the player graph peaks is a capacity story, not a bug.
• If your server is at its player cap every evening and the FPS holds, you have room to raise Max players. If FPS falls first, you do not.

6Tune the Rest

If the graphs look fine but the game still feels bad, the Advanced block in Rust settings has the levers:

• Tick rate and entity rate decide how often the server updates the world and the things in it. Higher is smoother and costs more.
• Save interval controls how often the world is written to disk. Every save is a brief pause, so a very short interval on a large world is felt.
• Max dropped items and the despawn timers keep loose loot from accumulating between wipes.

Change one at a time, and watch the graph for a day before changing the next.

Good to Know

• Plugins are a common cause. A badly written plugin can cost more FPS than a hundred players. If performance fell off after an install, that is your first suspect. See how to install plugins.
• Force wipe day is not a fair test. Everything is slower on the first Thursday of the month while Rust, Oxide and Carbon settle.
• One player complaining is not a server problem. Check whether the graphs actually moved. If they did not, ask that player to run an MTR so we can look at the route.

Finished

If the graphs show a real problem and none of the above explains it, open a ticket with the time it happened and what the Performance tab showed, and we will look at the machine.