
Do two Rust worlds stall when their saves overlap?
Two worlds can pause around the same time for several reasons. Collect one overlap and one quiet comparison from normal play. Observe the natural saves before you change a setting or force additional work.
Put both worlds on the same timeline
Ask a player on each world to report a brief delay in a server action, such as opening a container. Record each time in the same zone.
- Read each world's actual save times from the console or its active save file timestamps. Give the names and times to staff tracking the incident.
- Read host disk activity and memory across the same interval. A Linux host may expose I/O pressure under /proc/pressure/io. Use the disk view supplied by your host or Windows monitoring tools if you do not have that file.
- Mark anything else heavy in that interval, including a backup, scan or second world starting. Compare with an interval where one world saved alone with a similar player load.
Read the overlap against a comparison
A repeated time relationship is evidence for the next test. It does not identify the only bottleneck.
| Observed pattern | Next check |
|---|---|
| Both player symptoms line up with the two saves and higher I/O pressure | On spare worlds, arrange non-overlapping save work and repeat the player action with the same conditions. |
| The stall appears when neither world is saving | Check other scheduled jobs and whether a console or host measurement changed at the same moment. |
| Only one player's local view stutters | Check whether other players can repeat the same server action. Compare their connection and client behavior separately. |
Keep each world's recovery needs intact
If separation improves the comparison on the test host, decide whether you can move unrelated disk work or separate the worlds onto different storage or hosts. Preserve the save frequency you need to recover progress. After one change, repeat the timeline and make sure both worlds still complete normal saves.