A very nice update … the lack of a Linux server that runs well idle is still a sore spot.
Currently, running this game’s server executable idle under Linux, consumes about 30% CPU (between 20% for the game and 10% for WINE itself) on a i7 10700 … and that’s just too much to justify “leaving it running.”
To give a good relative benchmark, a modded Minecraft server runs at about 6% idle on this machine.
the lack of a Linux server that runs well idle is still a sore spot.
Ya, I have a dedicated server running in a docker container on my home “server”. The CPU is a i7-4790K and the enshrouded process is hogging 60-65% of the CPU time (according to top). The wineserver is actually pretty lite at 2-3%. And this is with no one connected. I’ve not tracked it while playing, but we do occasionally get “server overloaded” messages. Oddly, they seem more common when the server has been running a long while. So, I setup a cron job which stops and restarts the container every morning. Not an ideal solution, but it has reduced the number of times we’ve seen the “server overloaded” message.
I’ve just accepted that the game is in Early Access and it’s going to have the odd issue, especially when running under Linux. Still it’s perfectly playable (now that he keyboard/mouse issue is fixed) and a lot of fun. Maybe the Linux issues will get ironed out over time.
Yeah, it runs great for us under the processor I previously listed. I just don’t like burning the electricity for that while idle (the hardware is dedicated in my basement … and folks play infrequently).
I’ve contemplated designing some kind of mimicking proxy I could to activate various servers only when someone tries to use them and then shuts them down when they’re idle for over an hour… But effort 😅
A very nice update … the lack of a Linux server that runs well idle is still a sore spot.
Currently, running this game’s server executable idle under Linux, consumes about 30% CPU (between 20% for the game and 10% for WINE itself) on a i7 10700 … and that’s just too much to justify “leaving it running.”
To give a good relative benchmark, a modded Minecraft server runs at about 6% idle on this machine.
Ya, I have a dedicated server running in a docker container on my home “server”. The CPU is a i7-4790K and the enshrouded process is hogging 60-65% of the CPU time (according to top). The wineserver is actually pretty lite at 2-3%. And this is with no one connected. I’ve not tracked it while playing, but we do occasionally get “server overloaded” messages. Oddly, they seem more common when the server has been running a long while. So, I setup a cron job which stops and restarts the container every morning. Not an ideal solution, but it has reduced the number of times we’ve seen the “server overloaded” message.
I’ve just accepted that the game is in Early Access and it’s going to have the odd issue, especially when running under Linux. Still it’s perfectly playable (now that he keyboard/mouse issue is fixed) and a lot of fun. Maybe the Linux issues will get ironed out over time.
Yeah, it runs great for us under the processor I previously listed. I just don’t like burning the electricity for that while idle (the hardware is dedicated in my basement … and folks play infrequently).
I’ve contemplated designing some kind of mimicking proxy I could to activate various servers only when someone tries to use them and then shuts them down when they’re idle for over an hour… But effort 😅