-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server performance issues #258
Labels
Comments
connorhsm
added
bug
Something isn't working
help wanted
Extra attention is needed
labels
Dec 17, 2024
Here's a Valgrind dump, capturing the server startup using a copy of the current map. No players joined during this. |
Looks like I was initially wrong about the testing server results, Valgrind did find a notable memory leak which should soon be handled, as linked above. |
At 89%, adding another 2GB swap. Current 6GB swap + 4GB memory. Pending server update with potential fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A continuation of #151
See past 14 day view of metrics:
1. CPU usage (and thus load) spiking and staying at a high baseline
This is a long-standing issue and is of lesser concern than point 2. This issue rears its head typically ~2 weeks after a game server start. The update (and restart) predating this was December 3rd, see spiking begin December 11th. The usage is directly caused by the game server process, which sits at 100% usage on a single core, thus 50% baseline spike.
There isn't any measurable impact on player experience when this issue appears.
This can also be seen via htop:
Oddly, the process is reporting uptime of 8 days, which lines up roughly when the spiking began. Coincidence?
2. Memory usage continually marching up
Memory has typically been a slight concern. Though, from my memory, we first started having significant problems leading up to the most recent wipe (3rd November). We put this down to the map size and waited for the wipe. The rise of memory early in this map's lifetime was concerning, but we also hoped this would level out, it appears this is not the case.
This does inevitably cause the host machine to run out of memory and kill the game server process. Adding swap in previous testing appears to mitigate this to some degree. Suspected memory leak, now to find it 🙃
Action
The text was updated successfully, but these errors were encountered: