Chris Withers wrote:
Jim Washington wrote:
Has anyone done this?
I played wit hsetting it manaully in Task Manager a coupla times.
Hmm. Cannot do that here with python.exe. Maybe the process is running too long and spread over both processors, so affinity cannot be made at this point. It may be time to experiment.
Is the above procedure the correct way to do this?
Never heard of imagecfg before, and it's not official MS stuff, so maybe not :-S
The site says that imagecfg is from the MS Resource Kit. Even if it were directly from MS, it's still a "mystery meat" executable to me.
Like I say, it's a production machine, and I would rather not experiment. Which executable(s) should be imagecfg'd? Is it the python.exe in [zope]/bin? Or the .exe that starts the service? or a .dll or two?
Dunno. Why are you looking to do this? What problems are you experiencing?
No problems yet. But we're soon hosting something that has potential to use the machine a bit more, so it makes sense to take care of any easy-to-fix performance issues. Reading here and there, the machine is supposedly losing somewhere between 5 and 20 percent of efficiency due to the python global interpreter lock getting swapped between processors. Or something like that. Thanks for the response, Chris. It looks like I will have to do an experiment or two. I'll let the list know what I end up with. -- Jim Washington