the Linux version of DS has an exponential server FPS drop in multiplayer which depends on players number while the Windows one seems to be more stable on the same machine.
Description
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Linux x64
- Category
- Dedicated Server
- Start Arma 3 DS on Linux 64bit
- Connect 100+ players and put them on slots.
- Start mission and check server FPS.
more players - more FPS drop.
while we are experiencing low server FPS value it still consumes less RAM and less CPU compared to the Windows version.
Event Timeline
Connect 100+ players and put them on slots.
Cannot reproduce :D
I run ~30 players on my server and am not aware of such issues.
I have players enough to reproduce that and I can do tests for you if it's needed, the question is is Bohemia even interested in the Linux version because it looks far away from the windows one. There are lots of memory leaks and corruptions that maybe can cause to low fps
There are lots of memory leaks and corruptions
Huh where? How did you check that?
Are you running profiling branch performance build? there recently was a optimization for server networking.
I would need to get that many players onto my own server, for potentially a few hours to profile and debug issues.
Huh where? How did you check that?
In Linux development there is the most famous tool valgrind which allows to check an application dynamically with a verbose output. But regarding the Arma 3 DS binary it's enough to start and then terminate its process to see that something is definitely wrong (segfault).
Are you running profiling branch performance build?
I've installed the service with the following command
steamcmd +login $LOGIN +force_install_dir $A3PATH +"app_update 233780 -beta" validate +quit
I'm ready to provide you with the players if you are really going to fix that issue, you can write me in either Telegram or Discord to be able to talk more efficiently
I thought valgrind needed to be integrated into the binary, as we use custom memory allocation stuff.
I ran x64 linux server with address sanitizer for quite a while and fixed all (valid) issues that came up. Not aware of any leftovers.