DayZ Server Performance: Server FPS, Lag and Desync
Why DayZ servers slow down and what actually helps: infected and animal counts, loot nominals, persistent objects, restart cadence, and telling server lag from a player's connection.
How a DayZ Server Uses the CPU
DayZ's world simulation runs mostly on one CPU core. Some work, such as network replication, is spread over other cores, but infected, animals, physics and the loot economy all compete for that main thread.
- A DayZ server showing one core near 100% is normal, not a fault.
- More cores do not make a busy DayZ server faster. Reducing the work the main thread does does.
- When the main thread falls behind, server FPS drops, and players feel it as rubber-banding, doors and loot reacting late, and desync in fights.
Measuring Server FPS
- Resource usage monitor: the server's CPU and memory in the panel. See Resource Usage Monitor.
- The RPT log: with
logAverageFpsset inserverDZ.cfg, DayZ writes its average server FPS into the.RPTlog inprofiles/at that interval in seconds. Watch how it changes with player count and uptime. - In game:
serverFpsWarningsets the server FPS below which players see a warning.
A healthy server stays well above the warning level with a full player count. A value that drops steadily over hours of uptime points to object build-up, which restarts clear.
The Main Levers
| Lever | Where | Effect |
|---|---|---|
| Infected count | ZombieMaxCount in globals.xml | The biggest single lever. Lowering it frees CPU on every server |
| Animal count | AnimalMaxCount in globals.xml | Same idea, smaller effect |
| Loot quantities | nominal values in types.xml | Inflated nominals mean many more objects to track |
| Persistent objects | Bases, tents, barrels and vehicles in the save | Every one is simulated and saved. Hoarding servers slow down over weeks |
| Network ranges | networkRange* keys in serverDZ.cfg | Larger ranges send more objects to every player |
Change one lever at a time and compare server FPS over a similar player count, so you know what helped.
Keeping Object Counts Under Control
- Base decay: keep vanilla lifetimes and territory-flag timers, or shorten them, so abandoned bases disappear. See globals.xml: Cleanup and Base Decay.
- Vehicles: keep event
nominalandmaxmodest; wrecked and abandoned cars count too. - Loot: raise specific items, not everything. See DayZ Loot Economy Explained.
- Base limits: state them in your rules. A single mega-base with hundreds of storage items can slow the whole server when players are near it.
- Periodic world wipes: many communities wipe the world every few months for exactly this reason.
Restart Cadence
Uptime itself costs performance on DayZ: memory use and object counts grow while the server runs. Most busy servers restart every 3 to 6 hours with in-game warnings.
The platform's Automatic Daily Restart only restarts an empty server, so on a busy server plan restarts yourself. See Scheduled Restarts and Server Messages.
Players and Mods
- Player slots: each player adds simulation and network work around them. Vanilla is 60. If performance suffers at full capacity, a lower
maxPlayersgives a better game for the players who are on. - Script errors: check the
script_*.loginprofiles/now and then. A script writing errors many times a second costs CPU and fills the disk. Undo the mission edit that causes it, or open a support ticket. - Memory: if the resource monitor shows memory at your plan's limit, the server will stutter or crash. Reduce object counts, or talk to support about your plan.
When It Is Not the Server
If one or two players lag while everyone else is fine and server FPS is steady, the problem is usually their connection: Wi-Fi, packet loss or a bad route.
- Ask them to test with a wired connection.
- Have them run the test in the WinMTR guide against your server's IP and share the result.
If every player lags at the same moment and server FPS drops at that moment, it is the server, and the levers above apply.