This has the characteristics of a network problem, but it may be somewhere else. Users report that the system just seems to stop responding for a few seconds, then recovers. Of course, I've not been able to reproduce the problem nor isolate a command sequence that triggers it, but I am convinced that it's real. This, BTW, happens on a lightly loaded machine with no apparent resource problems. Any thoughts, pointers, or techniques to isolate the problem would be appreciated. Oh, yes, the environment.. Dual Athlon Barton Stepping CPUs AMD2600, Tyan Tiger Motherboard, 4GB memory, 4x120 3Ware RAID 10, ethernet feed. RH7.3 OS, Python 2.3.1, Zope 2.6.2b3. Any help appreciate. -dra
Dennis Allison wrote:
Oh, yes, the environment.. Dual Athlon Barton Stepping CPUs AMD2600,
Ouch. What're you doing to make sure Zope only uses one of those processors?
Tiger Motherboard, 4GB memory, 4x120 3Ware RAID 10, ethernet feed. RH7.3 OS, Python 2.3.1, Zope 2.6.2b3.
Any other products involved? Sounds like you might have processor affinity fun'n'games... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
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. On Mon, 22 Mar 2004, Chris Withers wrote:
Dennis Allison wrote:
Oh, yes, the environment.. Dual Athlon Barton Stepping CPUs AMD2600,
Ouch. What're you doing to make sure Zope only uses one of those processors?
Tiger Motherboard, 4GB memory, 4x120 3Ware RAID 10, ethernet feed. RH7.3 OS, Python 2.3.1, Zope 2.6.2b3.
Any other products involved?
Sounds like you might have processor affinity fun'n'games...
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
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
Thanks. I'll review the archives. -d On Tue, 23 Mar 2004, Chris Withers wrote:
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
Chris, Are there any tools which can be use to help isolate a problem such as the one I describe? There are a large number of different products involved & any one of them could be the culprit. On Mon, 22 Mar 2004, Chris Withers wrote:
Dennis Allison wrote:
Oh, yes, the environment.. Dual Athlon Barton Stepping CPUs AMD2600,
Ouch. What're you doing to make sure Zope only uses one of those processors?
Tiger Motherboard, 4GB memory, 4x120 3Ware RAID 10, ethernet feed. RH7.3 OS, Python 2.3.1, Zope 2.6.2b3.
Any other products involved?
Sounds like you might have processor affinity fun'n'games...
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Dennis Allison wrote at 2004-3-22 01:43 -0800:
This has the characteristics of a network problem, but it may be somewhere else. Users report that the system just seems to stop responding for a few seconds, then recovers. Of course, I've not been able to reproduce the problem nor isolate a command sequence that triggers it, but I am convinced that it's real. This, BTW, happens on a lightly loaded machine with no apparent resource problems.
Any thoughts, pointers, or techniques to isolate the problem would be appreciated.
Oh, yes, the environment.. Dual Athlon Barton Stepping CPUs AMD2600, Tyan Tiger Motherboard, 4GB memory, 4x120 3Ware RAID 10, ethernet feed. RH7.3 OS, Python 2.3.1, Zope 2.6.2b3.
If this is indeed Python 2.3.1 (and not Python 2.1.3), then you should upgrade your Python. Python 2.3.1 contained bugs triggered by Zope. -- Dieter
Latent dyslexia strikes again -- it's Python 2.1.3, the standard release with Zope 2.6.2. I typed Python 2.3.1 )-: <blush\> On Mon, 22 Mar 2004, Dieter Maurer wrote:
Dennis Allison wrote at 2004-3-22 01:43 -0800:
This has the characteristics of a network problem, but it may be somewhere else. Users report that the system just seems to stop responding for a few seconds, then recovers. Of course, I've not been able to reproduce the problem nor isolate a command sequence that triggers it, but I am convinced that it's real. This, BTW, happens on a lightly loaded machine with no apparent resource problems.
Any thoughts, pointers, or techniques to isolate the problem would be appreciated.
Oh, yes, the environment.. Dual Athlon Barton Stepping CPUs AMD2600, Tyan Tiger Motherboard, 4GB memory, 4x120 3Ware RAID 10, ethernet feed. RH7.3 OS, Python 2.3.1, Zope 2.6.2b3.
If this is indeed Python 2.3.1 (and not Python 2.1.3), then you should upgrade your Python. Python 2.3.1 contained bugs triggered by Zope.
-- Dieter
participants (3)
-
Chris Withers -
Dennis Allison -
Dieter Maurer