- User Since
- Dec 7 2014, 3:36 PM (355 w, 1 d)
May 10 2016
This is still broken.
Interesting, sqwishy, that means that it's likely the -client parameter in Linux that makes it time out.
I tried running everything from a separate folder alltogether to see if that changed things, but unfortunately it didn't. Setting up a VM seemed counterproductive given ARMA's ill nature toward VM:s performancewise.
This have been tested with 1.54 AND the latest perf v7
Still broken, perhaps related?
This is still an issue with v4, a virtual server and a dedibox with the same hardware assigned:
100 players (Arma 3 Epoch) server FPS: ~16-17 [dedibox]
66 players (Arma 3 Epoch) server FPS: ~10-15 (fluctuating) [VM]
Intel Xeon E3-1245v2 at 4.0 GHz ( Virtual Windows with 8 vCPUs and full CPU priority )
Preliminary test results 1.36 vperf1:
Server Uptime @ 5 mins = 40 Players = 45 fps
Server Uptime @ 10 mins = 46 Players = 45 fps
Server Uptime @ 15 mins = 48 Players = 38 fps @ 75% CPU Usage.
Server Uptime @ 45 mins = 60 Players = 18-21 fps @ 70% CPU Usage.
Confirmed, virtual machines running ARMA3 server do perform very poorly.
For the AI to be challenging at all, this needs to be fixed.
This is an issue, many conflicts in multiplayer happen over longer ranges and one side usually draw benefit from getting information they should not if the terrain was drawn correctly.