On Wednesday 03 of October 2007 20:17:45 Theo Macris wrote: > -- > [ Picked text/plain from multipart/alternative ] > CentOS4 x86 > CONFIG_HZ....That does not seem to be a part of my config. > > [EMAIL PROTECTED] boot]$ cat config-2.6.9-55.plus.c4smp|grep -i hz > CONFIG_MACHZ_WDT=m > > I did come up with some "similar" stuff via freq: > > [EMAIL PROTECTED] boot]$ cat config-2.6.9-55.plus.c4smp|grep -i freq > # CPU Frequency scaling > CONFIG_CPU_FREQ=y > # CONFIG_CPU_FREQ_PROC_INTF is not set > # CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set > CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y > CONFIG_CPU_FREQ_GOV_PERFORMANCE=y > CONFIG_CPU_FREQ_GOV_POWERSAVE=m > CONFIG_CPU_FREQ_GOV_USERSPACE=y > CONFIG_CPU_FREQ_GOV_ONDEMAND=m > # CONFIG_CPU_FREQ_24_API is not set > CONFIG_CPU_FREQ_TABLE=y > # CPUFreq processor drivers > CONFIG_X86_ACPI_CPUFREQ=y > # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set > # Wireless 802.11 Frequency Hopping cards support
Forget all crap about kernel time resolution having anything to do with application performance. Anything above 100Hz may (because of linux scheduler inefficiency) have good influence on desktop computer and not on server app. Higher timer means more frequent process rescheduling and more involuntary context switches and that means lower performance. All you can do is wait for better process scheduler inside linux kernel. -- Mariusz Zielinski _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
