06-28-2009, 01:21 PM
I run a multicore system for my servers and was curious to if I should run srcds normally, or assign each srcds a individual core (i use fire daemon to do this).
General SRCDS question
|
06-28-2009, 01:21 PM
I run a multicore system for my servers and was curious to if I should run srcds normally, or assign each srcds a individual core (i use fire daemon to do this).
06-28-2009, 01:30 PM
If you just run SRCDS on its own, it will load balance correctly (as far as I've tested). But feel free to try for yourself, as it may depend on your system
06-28-2009, 01:32 PM
Beaverbeliever Wrote:If you just run SRCDS on its own, it will load balance correctly (as far as I've tested). But feel free to try for yourself, as it may depend on your system I was under the impression that it will only run one one core per instance and it picks the core at random.
~ trewq
06-28-2009, 01:34 PM
King Goilio Wrote:Beaverbeliever Wrote:If you just run SRCDS on its own, it will load balance correctly (as far as I've tested). But feel free to try for yourself, as it may depend on your system All of a sudden that sounds familiar. I think your right
06-28-2009, 01:49 PM
Windows will also automatically load-balance from what I've read. (So if a core gets too busy it will switch cores.) While it's mixed, I would say try NOT defining a core. If you notice lag at times, try defining a core.
~ Mooga ...w00t? - SRCDS.com on Twitter
Please do not PM me for server related help fqdn Wrote:if you've seen the any of the matrix movies, a game server is not all that different. it runs a version of the game that handles the entire world for each client connected. that's the 2 sentence explanation.
06-29-2009, 02:40 AM
If you run 4 servers then yes, assign a core to each of them, however if you want to, you can assign more than 1 core to srcds so other cores don't get busy.
/affinity # is startup command Ok from what i have tested (based on a 4 core system on server 2003) basically all this is doing is telling srcds which cores it can use and if one of the cores are overloaded it switches to a different one #1 : Core 1 #2 : Core 2 #3 : Core 1,2 #4 : Core 3 #5 : Core 1,3 #6 : Core 2,3 #7 : Core 1,2,3 #8 : Core 4 #9 : Core 2,4 #10 : Core 1,4 #11 : Back to Core 1 (didnt test anything past 10) |
« Next Oldest | Next Newest »
|