Interesting - thanks for that link - although not useful to use for UniData sounds like!! Every user would start "udt.exe" and be condemned to a single processor unless you had a 'special' udt4.exe that bound to processor 4 while the other udts floated -- but still - I can't think of a benefit to bind ourselves to a processor in our current settings.
I'm VERY pleased to know we're actually getting the benefit of the multi-processor setup. I couldn't figure out with shared memory why the udt.exe would actually care which processor it ran against - but it's one of those things I just took as a fact and never thought about. DW -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Beahm Sent: Wednesday, October 26, 2005 8:04 AM To: [email protected] Subject: RE: [U2] UniData and multi-core chips. FWIW, I have seen a UniVerse process jump from one CPU to another on a dual-CPU box running NT 4. It was a big process and we were logging system monitors to identify bottlenecks -- Rich Taylor might (or might not, as it was years ago) remember helping us with our investigation. A quick search shows how to set processor affinity permanently for an application if the opposite behavior is desired: http://searchwin2000.techtarget.com/tip/1,289483,sid1_gci778853,00.html > Date: Tue, 25 Oct 2005 19:48:31 -0500 > From: "David Wolverton" <[EMAIL PROTECTED]> > Subject: RE: [U2] UniData and multi-core chips. > > For Windows the processes float? Interesting!! I was just reporting > what we were told eons ago -- that Processes were bound to a CPU on on > startup on a Windows MultiProcessor... If that's not the case, even better ... > Information in this area is hard to come by -- any authoritative information > is welcome!! Where can we find more information on this? > > > "When you start up, in the case of a dual/quad-processor, my > understanding is that process is 'bound' to whatever CPU the OS kicked > it off on... So, in theory, you do get some advantage of multiple > processors, but the load is not dynamically balanced based on usage. > .... > This is NOT how it works. The OS is able to start a process on a > particular CPU and then can move the process on to other CPU's as it > sees fit, to manage the load. E.g. does dynamically balance based on > usage. There are OS commands to "bind" processes to CPUs, but these > should not normally required, you are best to leave it up to the OS! ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
