Dennis Allison wrote:
While it's possible, the scheduler is pretty good at maintaining processor affinity without intervention. I have *never* seen anything which would suggest that is a problem. This is happening on an unloaded system when processor affinity issues should be hard to trigger.
Okay, but I have lots of memories of reading about problems with Python's Global Interpretter Lock and lightly loaded multi-processor machines. The mailinglist archives may give more of a clue. One thing you could try is to get a ZEO storage server up and running, then run up 4 or 5 ZEO clients, but each with only one thread. Then you just need to figure out how to round-robin them so they all appear through one port... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk