Ive just had some time to read the logs to find the RDTSC_FREQUENCY and
it was rather easy.
[code]
/HLDS installation up to date
Running a benchmark to measure system clock frequency...
Finished RDTSC test. To prevent the startup delay from this benchmark,
set the environment variable RDTSC_FREQUENCY to 2400.000000 on this
system. This value is dependent upon the CPU clock speed and
architecture and should be determined separately for each server. The
use of this mechanism for timing can be disabled by setting
RDTSC_FREQUENCY to 'disabled'.
Using breakpad minidump system/
[/code]
In this case should I add this to server.cfg or ?
[code]
/RDTSC_FREQUENCY 2400.000000/
[/code]
But how is the recommendations to make the servers to use the cpu:usage
as before the update ?
It would be nice to hear some info from the dev.team or someone close :)
Peter
Sweden
------------------------------------------------------------------------
Ps. my previus post
/We have machines with both Debian and Fedora srcds-servers running and
all is showing high spu usage.
Its both TF2 and DoD:S running on them and we monitor all with munin.
This is a pic from a debian 64-bit server with 4 cores Xeon running 2
dods servers.
http://url.dayofdefeat.se/pics/cpu-week-Ferm.png
uname -a: Linux-2.6.33.5-rt23-ub-100hz #1 SMP PREEMPT RT Wed Jul 14
13:41:19 CEST 2010 x86_64 GNU/Linux
This is a pic from a Fedora server running 1 dods + 2 TF2 servers on 4
cores.
http://url.dayofdefeat.se/pics/cpu-week-Trelle.png
uname a: Linux-2 2.6.34 #1 SMP PREEMPT Thu Jul 22 10:33:46 CEST 2010
i686 i686 i386 GNU/Linux
I do hope its possible to find the problem.
Peter
Sweden /
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
