problem.. help!

[memelo]

Hello, I'm having trouble with server "bigslot".
Information from my system:

Code:

processor       : 7
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Xeon(R) CPU           X5460  @ 3.16GHz
stepping        : 6
cpu MHz         : 3166.720
cache size      : 6144 KB

16gb RAM

Linux debian 2.6.33.5-zen3-ub-100hz #1 ZEN SMP Tue Jul 6 19:15:06 CEST 2010 x86_64 GNU/Linux (ulrich-block)

1000      3260 21.3  1.0 304016 167364 pts/2   Rl+  Aug10 346:02 ./srcds_linux -console -game cstrike -ip x.x.x.x -port 27015 -maxplayers 54 -tickrate 66 +fps_max 0 +map de_dust2 +servercfgfile server.cfg -sport 29000

top - 19:21:25 up 1 day, 13:37,  1 user,  load average: 1.13, 1.20, 1.27
Tasks: 103 total,   2 running, 101 sleeping,   0 stopped,   0 zombie
Cpu(s): 13.2%us,  0.0%sy,  0.0%ni, 86.6%id,  0.0%wa,  0.0%hi,  0.1%si,  0.0%st
Mem:  16472820k total,  8093772k used,  8379048k free,   131456k buffers
Swap: 11904124k total,        0k used, 11904124k free,  7220860k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
3260 css27015   0   0  296m 163m  19m R   96  1.0 372:25.81 srcds_linux
5185 css27015   0   0  237m 105m  19m S   10  0.7  14:36.51 srcds_linux
5078 css27015   0   0  223m  91m  19m S    2  0.6   1:47.24 srcds_linux

link: 100mbps

The FPS server is the following:
CPU In Out Uptime Users FPS Players
99.61 217448.64 640243.88 1623 11 33.28 49

CPU In Out Uptime Users FPS Players
49.42 227090.14 728347.62 1623 11 35.73 49

CPU In Out Uptime Users FPS Players
99.53 229164.06 673541.94 1623 11 24.74 49

CPU In Out Uptime Users FPS Players
99.03 212615.27 691290.94 1630 11 53.54 44

CPU In Out Uptime Users FPS Players
98.84 210927.95 697060.44 1637 11 34.76 46

http://www.fpsmeter.org/p,view;84430.html

with 46 players playing / 54

I am running 2 other servers on the same server.

1001 5078 1.5 0.5 221584 85892 pts/3 Sl+ 17:25 1:21 ./srcds_linux -console -game cstrike -ip x.x.x.x -port 27015 -maxplayers 30 -tickrate 66 +fps_max 0 +map de_dust2 +servercfgfile server.cfg -sport 29000

1002 5185 21.8 0.6 243404 108508 pts/4 Sl+ 18:04 10:50 ./srcds_linux -console -game cstrike -ip x.x.x.x -port 27015 -maxplayers 60 -tickrate 66 +fps_max 0 +map de_dust2 +servercfgfile server.cfg -sport 29000

The rate is low, occurring lag, what can I do?

Thanks.

[memelo]

CPU utilization is high too!

[BehaartesEtwas]

yes, it seems, your CPU is overloaded (don't look at the CPU load in stats or top or so, that's all wrong. but the fps pattern is quite typical).

question: why do you have such dramatic jumps in the number of players? typically I would expect the player number to increase or decrease in small steps of 1 or 2, not by 10 or 12... you don't use bots, do you?

what you can try: disable hyperthreading in BIOS to ensure you have the maximum performance per core. reduce the tick rate (sv_maxcmdrate 33 and sv_maxupdaterate 33 - you can omit the -tickrate option at command line, it doesn't exist anymore) and the fps (fps_max 100 or even lower).

and never use bots for testing. they consume much more cpu but in a very different way.

[memelo]

@BehaartesEtwas I'm not using bot.
sys_ticrate and pingboost can help me with something?
the rate comes at a time stable at 30~50 but sometimes reaches 12 causing the lag.
the reason for the lower rate? influence of FPS? CPU overloaded?

the FPS is normal 50 ~ 30?

thanks

[BehaartesEtwas]

sys_ticrate and pingboost do not exist for srcds (only for hlds). sys_ticrate got replaced by fps_max.

the low rates are caused by severe fps drops which are probably caused by a cpu overload. I recommend not looking (too much) at the cpu load (it's very inaccurate even in top or htop or such linux commands). instead you should try getting the fps stable. as stability is much more important than the actual height (as long as it is above the tick rate) you might want to get it lower. I wrote you some advises above. Please try it out. You will need to play around with those settings a while, nobody can tell you what is optimal in your case.