I can't even upload the logfile to show ya'll cause it's too big to upload.

Hello SoulsAggro.
Can you please provide the IP/ID of the affected server and would you be okay with us removing the excess logfiles?

@SoulsAggro If you actually get this done and this makes your server performance better, let us know.

It's literally every server and I did ask Nitrado to delete them from mine (no response)
service_id: 16883716 ip: 128.0.114.204:11300
service_id: 15770527 ip: 95.156.238.151:11200

I'd love for you to remove the excess logfiles, especially the 2.8gb file

In T192790#2827764, @TheRealTDog wrote:

@SoulsAggro If you actually get this done and this makes your server performance better, let us know.

Absolutely, I’ll report back if this gets resolved, but removing or rotating the server.log will absolutely improve performance, here’s why:

Right now my 32-slot server has a server.log file that’s over 2.8GB. This isn’t just some minor text file sitting around:

• The DayZ server constantly writes to this file.
• The bigger it gets, the more disk I/O the server is forced to do, and the more memory gets used if any process tries to read it (even for log parsing, or scheduled scripts).
• The file is never rotated, truncated, or cleared—it only ever grows.

Neither the server owner nor most admins even know it exists, and there’s no option to delete it from Nitrado’s panel or FTP.
When you have a huge log file like this, it can actually slow down the game server process itself—especially on these budget/virtualised hosts. It also makes every maintenance operation (like Nitrado’s own scheduled backups, file checks, and FTP accesses) slower, because they have to scan through this giant file every time.
To open this file currently, I have to split it into 11x 250mb files, no normal text editor can even open it.

So yeah, deleting/truncating this file regularly would:

• Reduce disk usage and I/O lag,
• Decrease load times for any log-related task,
• Lower the risk of server crashes or stutters from resource exhaustion,

And generally make the server more responsive, especially during restarts and heavy activity.

Most people never even look at this log, so having a multi-gigabyte file just sitting there is pointless and harmful.
If they ever implement real log rotation, or at least let us clear it, everyone’s server would run smoother—no exaggeration.

This isn’t just a minor cleanup, it’s an actual performance fix for every server.

Nitrado did reply apparently, I just missed it, they closed the ticket then marked it as I closed it. So much for "waiting for my response".
(They always do this, I've complained about it before. 8 years and nothing's changed)

I asked them if they could permanently delete the file and they said this.

I'd love for you to remove the excess logfiles, especially the 2.8gb file

Will do, please count with some downtime while this is done. Should be brief though.

In T192790#2831725, @SoulsAggro wrote:

It's literally every server and I did ask Nitrado to delete them from mine (no response)
service_id: 16883716 ip: 128.0.114.204:11300
service_id: 15770527 ip: 95.156.238.151:11200

I'd love for you to remove the excess logfiles, especially the 2.8gb file

Removed from both, please let us know if that has improved the performance.

Average before deletion: 64.34%
Average after deletion: 38.96% → Massive drop in overall CPU load.

Average before deletion: 4946.95 MB
Average after deletion: 4724.20 MB → RAM use dropped by ~223MB.

Players reporting smoother server, less desync, less crashes & faster restarts

In T192790#2832691, @SoulsAggro wrote:

Average before deletion: 64.34%
Average after deletion: 38.96% → Massive drop in overall CPU load.

Average before deletion: 4946.95 MB
Average after deletion: 4724.20 MB → RAM use dropped by ~223MB.

Players reporting smoother server, less desync, less crashes & faster restarts

Thank you, we made further changes to test this problem. Currently, the server.log will not be generated anymoreso theoretically, the CPU usage should decrease and stay on that lower level the whole time.
Please let us know so we can confirm or deny if this is the case or if it was caused by something else.

Looks like the 10slot server isn't generating the server.log file but it looks like the 32 slot server is still, both have better looking CPU, I grabbed the CPU, Players and RAM json from Nitrado for you

32 Slot:

10 Slot: