So you augment it to change the cpu affinity based on the cpu's load at the instant the server is started, really what use is that? Its a single snapshot in time of a rapidly changing environment so its almost guaranteed to make the wrong decision.
You could build static load metrics based on massive sample sets to get a basic idea of average loading of a specific server but it would never take into account important facts like map loads, server startup, runaway processes etc. Choosing which CPU is best to run a process is exactly what the scheduler in the OS is designed for. It has access to all the information needed to make the best decision at any given point in time. Any manual process no matter how complex will never come close and is why dynamic schedulers where invented many many moons ago and is why I have no intention of wasting development resources on reinventing the wheel. ----- Original Message ----- From: "Dustin Tuft" <[EMAIL PROTECTED]>
Well I guess you have a limited imanigation. The first place I would start is your process where an admin clicks to start a new server or shut down a server. I asume that you have an existing structure in place that manages this now? so maybe I gave you to much credit, If you have a structure in place then the ease of making it a smarter process is an addtion to your exsiting function on that given server to check the load of all CPU's and set affinity, even say not this server go to the next server in the list. I didn't say anything about recoding the schedular for windows, I only express that I have felt the pian in multi threaded applications that have critical events dependent on proper timing, and in most cases your have to have one threaded process monitor all threads to get anywhere close to correct timing, but that again could lead to lag here, lag being the reality that your waiting for something before you move on.....
================================================ 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 (023) 8024 3137 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
