Page MenuHomeFeedback Tracker

[0.9.5.61] ArmaReforgerServer.exe - Odd memory usage reported in server log files.
Closed, ResolvedPublic

Description

I am seeing some odd data being reported via the game-server log files, specifically a jump in the reported memory in use is recorded in the console.log file output when using the -logStats launch parameter.

The process data recorded at the same time from the OS has recorded no such jump in memory use - Although the process has consistently reported higher memory usage than the log files since the game was opened to the public, so process memory usage recording has been consistent in that respect.

Both of these occurences coincided within a normal dip/peak in cpu time/usage at the time of recording, you cannot see it in the graphs provided below from the other regular dips/peaks in cpu-usage so it does not appear to be doing anything abnormal in respect of cpu usage when this happens.

(I have stripped the non-logStats log records from the following two instances for clarity)

First spike in memory usage of ~726MB between 06:16 - 06:18 AM (UTC+1):

06:16:42:098   DEFAULT      : FPS: 60.0, frame time (avg: 16.7 ms, min: 12.5 ms, max: 20.6 ms), Mem: 4110426 kB, Player: 0, AI: 56, Veh: 0 (15), Proj (S: 0, M: 0, G: 0 | 0), RplItemsS: 340
06:18:42:113   DEFAULT      : FPS: 60.0, frame time (avg: 16.7 ms, min: 12.9 ms, max: 20.1 ms), Mem: 4837357 kB, Player: 0, AI: 56, Veh: 0 (15), Proj (S: 0, M: 0, G: 0 | 0), RplItemsS: 340

Second spike in memory usage of ~317MB between 17:02 - 17:04 PM (UTC+1) :

17:02:43:667   DEFAULT      : FPS: 60.0, frame time (avg: 16.7 ms, min: 13.2 ms, max: 19.9 ms), Mem: 3901336 kB, Player: 0, AI: 56, Veh: 0 (15), Proj (S: 0, M: 0, G: 0 | 0), RplItemsS: 340
17:04:43:682   DEFAULT      : FPS: 60.0, frame time (avg: 16.7 ms, min: 13.4 ms, max: 20.1 ms), Mem: 4218801 kB, Player: 0, AI: 56, Veh: 0 (15), Proj (S: 0, M: 0, G: 0 | 0), RplItemsS: 340

Notes about this game-server:

  • This is a passworded/private game-server which was compeltely empty of players for the duration of these graphs.
  • The server is scheduled to restart every 12 hours, once at 1200 (midday) and again at 0000 (midnight) UTC+1, which you can see in the graphs.
  • -logStats is is set to 120000ms (2 minute intervals)
  • This game-server exeecutable has cpu affinity set to lock it to using 2 cores / 4 threads.
  • The server is running with 64 player slots, -maxFPS 60, with fastValidation: true and battlEye: true set in the servers JSON config file.
  • The server is running the vanilla Conflict whole island campaign with AI and no mods.

This was not happening with the previous build of the game-server and nothing else unusual was reported in the log files other than these jumps in memory use reported by the server in its logfile over the course of 2 seperate restarts.
I also would not have spotted this if it wasn't on a graph, manually scanning days worth of log-file data for odities is not something I'm into.

Graphing using Grafana:

Details

Severity
Minor
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
Windows Server 2019 Standard [10.0.17763 Build 17763]
Category
General
Steps To Reproduce

Start up a game-server on a dedicated server with the settings described above and observe the console.log file's recorded stats over a 24-48 hour period.
So far since the 0.9.5.61 game build update this appears to be consistent behaviour.

Event Timeline

Uro created this task.Jun 3 2022, 4:42 AM
Uro added a comment.Jun 3 2022, 6:15 PM

An update to add, the game-server has not reported this memory usage spike in the logfile since I created this ticket.

My current theory is that it is something backend/api/http related, such as one of those services restarting and a spike/build-up of those requests in the game-server due to getting a non-response from those master-services over the 120000ms reporting interval, this is only a theory as I have no data to base this on.

Geez changed the task status from New to Assigned.Jun 8 2022, 5:00 PM

This should be already resolved

Geez closed this task as Resolved.Jul 22 2022, 9:04 AM
Geez claimed this task.