Chris Oryschak wrote:
For the longest time I've been running multiple servers on a single box that has multiple cores. Each SRCDS instance would be assigned it's own core to prevent it from hopping between cores as I assumed they might overlap and max out that core. Plus I remember discussion of lag spikes occurring when it moves between cores.
Unless you think you can outsmart the scheduler in your system, don't try; you probably won't make things better, and you will probably make things worse.
My advice: don't use taskset to define cpu affinity for a process unless you have a good reason to do it and you know what you are doing.
Setting process affinity to a core can have a positive impact in certain situations, but the OB/scrds engine is probably not one of them, unless cache misses are a big deal.
Here are my questions: -Those of you who run multiple SRCDS instances per server, do you assign them each to a core?
No, I don't. This isn't the kind of application which would benefit from that kind of thing. Also, in my particular case, doing this would almost certainly be detrimental to performance.
-Do you renice any processes?
Yes I do, and yes, lowering the nice/raising the prio has a measurable positive impact on performance as measured on client net_graphs and end-user perception (me).
My advice: Definitely lower the nice on your srcds processes: "renice -10 $GAMESERVPID"
-Do you change the realtime scheduling?
Absolutely not. Realtime scheduling does not even make theoretical sense for this kind of application, especially not multiple realtime apps running on the same hardware.
I'll just say it: anyone who thinks realtime is a good idea for game servers is an idiot.
-- # Jesse Molina # Mail = [email protected] # Cell = 1-602-323-7608 _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
