Ian Griffiths wrote: > > I think John's point was that this might cause > > MSCORSRV.DLL to be used when > > MSCORWKS.DLL would have been better > > - the server version is designed to > > exploit multiprocessor boxes isn't it? >
Mike Woodring wrote: > > I doubt that setting affinity would do anything to alter > which version of the runtime was used That's the point! Yes, setting the affinity won't affect which version is used, but the fact is you probably *want* it to! You'll get the one you would have got in any case. But you probably don't want it - if you're planning to nobble the process to 1 processor, you probably want to be running with the version of the CLR that is designed to run best on 1 processor systems. It's the fact that the behaviour will *not* be affected by changing the processor affinity that's the problem. Not a big problem, as you say - it won't compromise program correctness. It's just that if you're twiddling with affinity, it's presumably to try and improve performance, so you're also likely to care about which version of the CLR you get. When MSCOREE knows it'll only have 1 processor, it always selects a particular version of the CLR, presumably for a good reason. So I was just trying to point out that if you find yourself in a situation where MSCOREE might think it'll get 2 processors where in fact it'll only have one, you might want to do something to make sure you get the right version of the CLR because by default, as you point out, you won't. -- Ian Griffiths DevelopMentor =================================== This list is hosted by DevelopMentorŪ http://www.develop.com You may be interested in Guerrilla .NET, 24 March 2003, in London and Boston http://www.develop.com/courses/gdotnet View archives and manage your subscription(s) at http://discuss.develop.com
