PDA

View Full Version : CS GO Server on Debian: high CPU usage


HTPProXy
04-22-2016, 02:51
Hello there,

I installed a CS GO server on my root server with minimal debian. I also installed sourcemod.
When starting the server the CUP usage is about 4%, but as soon as a player connects, the usage goes up to at least 50%. Yesterday there were 3 players on the server and I noticed that the ping was quite high. As soon as 2 players disconnected, the ping went down by about 20ms. I guess the bad ping is related to the high CPU usage.

The CS GO server is started with those params:
./srcds_linux -game csgo -console -usercon +game_type 0 +game_mode 0 +mapgroup mg_active +map de_dust2


The only content in my autoexec.cfg is
hostname "wonttellyou"
sv_setsteamaccount 12345...
rcon_password "wonttellyou"
sv_password ""
sv_cheats 0
sv_lan 0


The machine itself should have enough power to run the server without any issues:
Intel® Core i7-6700
64 GB DDR4 RAM
2 x 2 TB SATA 6 Gb/s 7200 rpm
1GBit connection

I cannot believe that a CS GO server really needs so much power. Are there any advices?

Cooky
04-22-2016, 03:05
That CPU is doing much with 'power saving' or 'geen technology'. I assume you're on a shared 1Gbps connection? You can run a speedtest to test your upload speed and verify if that causes the high ping.

The i7-6700 runs at 800Mhz when there is really nothing to do. If it uses more resources, the clockspeed will get a little higher. It depends how much the CPU needs.

I was a little shocked to when I saw my CPU usage was on 60% with 10 players, but that was with just 800Mhz. When there were 15 players it goes up to 1100Mhz and the CPU usage was 40% etc. etc.

You should test your clockspeed with:
sudo cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq

HTPProXy
04-22-2016, 03:27
Hello Cooky,

thank you for the answer. I think you are right, the server returns me this:
root@Debian-84-jessie-64-minimal /home/steam/steamcmd/cs_go/csgo/cfg # cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq
800000
800000
800000
800000
800000
800000
800000
800000


At the moment there is no one on the server, I will check the frequency later as soon as there is some traffic.

My provider guarantees a 1GBit connection, and I was able to download some bigger files with ~40MB/s. While the speed seems fine, the pings are not so good. On official Steam-Servers my ping will be ~30ms while on my own root server (which is only 100 miles away) I normally get ~50ms.

Im am not sure if my provider would care if I open a ticket because of the 'bad' pings :)

Cooky
04-22-2016, 03:33
It also depends on your tickrate and the routing from your home to your provider. You could also do a MTR from your local machine to your server.

Note: the CPU will run at 800Mhz up to 10-15 players.

Edit: OVH?

HTPProXy
04-22-2016, 03:56
The routing to others servers seems fine, my poor DSL connection pings google.de with ~25ms, while my root server responds after ~45ms. I just wrote a ticket to the provider (Hetzner), the answer was quite short: Out network is not latency-optimized..

Maybe I should try some other hosters as well ;)

Cooky
04-22-2016, 04:01
PM me for some other good providers. I'm also working for one of them.

Neuro Toxin
04-22-2016, 05:18
Routing has nothing to do with high CPU usage.

Cooky
04-22-2016, 05:25
Routing has nothing to do with high CPU usage.

Was about the higher latency.. :)

Bacardi
04-22-2016, 17:30
Good post.

Disabling Intel Speed Step from BIOS keeps CPU frequency full all the time.That CPU is doing much with 'power saving' or 'geen technology'. I assume you're on a shared 1Gbps connection? You can run a speedtest to test your upload speed and verify if that causes the high ping.

The i7-6700 runs at 800Mhz when there is really nothing to do. If it uses more resources, the clockspeed will get a little higher. It depends how much the CPU needs.

I was a little shocked to when I saw my CPU usage was on 60% with 10 players, but that was with just 800Mhz. When there were 15 players it goes up to 1100Mhz and the CPU usage was 40% etc. etc.

You should test your clockspeed with: