Page MenuHomePhabricator

Server Performance Drop Off After Restart
Acknowledged, NormalPublic


A few months ago I noticed this problem emerge, server performance after a server restart drops off massively. Ex. Server FPS is 12 before restart, after the restart it will drop down to 2-3 and very slowly increase back to roughly 6-9 by the time the next restart is about to hit. My server operates on a 4 hour restart schedule, the problem is much more apparent when the server is full, 60/60. Here is a video of performance stats on my server before/after multiple server restarts over about a week. As you can see, performance drops massively after each restart.


Operating System
Windows 10 x64
Steps To Reproduce
  1. Fill up a server (60/60)
  2. Gauge server performance over the course of a few hours
  3. Restart the server
  4. Watch server FPS carefully as it drops drastically

Event Timeline

jakon72 created this task.Oct 24 2017, 7:28 PM
Geez changed the task status from New to Assigned.Oct 25 2017, 11:04 AM
Geez added a subscriber: Geez.

Hello jakon72 and thank you for the report.
We are going to test this internally and we will let you know under this ticket once we have more information on the progress or in case we need some more information from you.

Geez changed the task status from Assigned to Need More Info.Oct 30 2017, 11:01 AM
This comment was removed by Geez.
Geez added a comment.Oct 30 2017, 11:59 AM
This comment was removed by Geez.
Geez added a comment.Oct 30 2017, 1:46 PM

Hello again jakon72.
We will have to restart your server couple of times due to testing, please notify your players that the server may be restarted more often than usual. Also, if the players can connect immediately after the restart, it would help us a lot with the testing.

Apologies, I just saw your comment. I hope everything went well and you were able to gather good data. If you need me to let my playerbase know of any further unscheduled restarts, please let me know.

Geez added a comment.Nov 1 2017, 9:44 AM

Hello jakon72.
The testing has not started yet as we were waiting for your response. If you do not mind then we would like to make the tests as I have mentioned.

Sure, you may go ahead with the tests. I will inform my community.

Has there been any progress made with this issue? Anything that you might be able to share?

Geez added a comment.EditedNov 7 2017, 12:57 PM

Hello jakon72.
So far there is no new info on the issue that we can share, however, the testing is still ongoing.

Geez added a comment.Nov 8 2017, 11:36 AM

Hello jakon72.
We would like to ask, are you doing some specific events on the server often? If so, do they involve multiple players logging on at the same place at the same or approximately the same time? If not, is there a possibility that there are large groups of players that log on at the same time onto the server in the same area of the map?

We have stopped doing events on the server a few months ago due to the shear amount of work and stress involved. To my knowledge, there aren't any groups of 6+ that are currently active on the server. I would guess that the maximum amount of players that might log onto the server in one specific area is 4-5. that is assuming that an entire squad is logging onto the server at the same time, in the same place, which probably doesn't happen very often.

This issue is still very apparent, just a moment ago the server was running on 1 FPS. Here's a screenshot. Are there any updates that can be shared?

Geez added a comment.Nov 20 2017, 12:02 PM

Hello jakon72.
Was the server running at 1 fps right after the server restart? Or has it dropped over some amount of time (how long approximately?)?

It dropped down to 1-2 FPS right after restart, as soon as the server filled back up, (60/60) performance dropped.

Geez changed the task status from Need More Info to Acknowledged.Nov 23 2017, 11:27 AM

Thank you jakon72.
We have determined a possible cause of the issue, however, implementing a hotfix would be too problematic and time consuming as the part that is the source of the issue is going to be replaced completely in the 0.63 version.