--
[ Picked text/plain from multipart/alternative ]
The CPU usage varies mildly between 2.4 and 2.6, but 2.6 definately responds
better with things like setting preempting in the kernel config and the fact
it is 1000Hz by default (though you can easily make a 2.4 kernel 1000Hz).

We run no more than 2 processes per CPU regardless of spec (except with the
AMD64 box we're playing around with, it's running 3 servers happily). Any
more than that and the servers start to suck when they're all full. Most of
our servers are either AMD XP 2700/2800's or P4 3.06's, and have 512MB RAM,
apart from two of the machines running srcds as it gets a bit piggy on RAM.

The settings we've found best for smooth play and accurate hitboxes is
setting tickrate 66 (100 is overkill for internet play when you take latency
of residential connections into account), and sv_minupdaterate/maxupdaterate
to 100, as well as sv_minrate/maxrate to 20000 as well. Bandwidth usage is
significantly higher with these settings (we went from 8Mbit in/out at peak
to 14Mbit in/out at peak), and will place significantly more strain on your
routers due to the additional number of packets, but the smooth gameplay is
definately worth it.

So to answer your question in the first post: "So all I'm asking is: is
using a kernel 2.4 and so reducing cpu usage a
"right" way to handle cpu usage issues with tickrate 100?"

No, the CPU usage difference is relatively small, and not enough to allow
you to get another server running on the machine. 2.6 does respond faster,
due to preempting and so on - and if you are able to use it then you will
get a better experience ingame.

-Scott

On 11/14/05, Jens Werner <[EMAIL PROTECTED]> wrote:

> Anyone else who could tell me about similar experiences with srcds?
> Since my suggestions came from such srcds I, of course, want to know
> that as well.
>
--

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to