Thanks Alfred, never had any real issue with the OS scheduler picking CPU / Core
here, well apart from X2's playing up if you don't install the "CPU driver".
There's always a little performance drop due to cache misses when bouncing
between
cores / cpu packages, but nothing compared to only being able to use 1 out 8
Core's :)
Regards
Steve
----- Original Message -----
From: "Alfred Reynolds" <[EMAIL PROTECTED]>
> It means we don't call SetAffinity() so the server will go to the CPU
> the OS decides (and wander among CPU's). You may want to test the
> performance impact of letting it wander and use your own script to bind
> it to the CPU of your choice if that helps.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the
person or entity to whom it is addressed. In the event of misdirection, the
recipient is prohibited from using, copying, printing or otherwise
disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
