RE: [Zope] high loads, more threads, spinning wheels

2005-05-02 Thread Jim Abramson
Thanks Stefan Jens... if yes, would upping the number of ZODB connections effectively raise the ceiling - e.g. 12 ZODB connections - 12 threads should perform properly ? Is increasing the number of ZODB cx's possible, let alone advisable? (why the default of 7 - not 6 or 8?)

Re: [Zope] high loads, more threads, spinning wheels

2005-05-02 Thread Stefan H. Holek
I assume what you see are hangs i.e. Zope appearing to not accept new requests, as soon as all 4 worker threads are busy waiting for the RDBMS system to answer. Now, using more threads will push back the point of unresponsiveness, but as soon as you have the 13th request hitting Zope, you are

Re: [Zope] high loads, more threads, spinning wheels

2005-05-01 Thread Stefan H. Holek
On 29. Apr 2005, at 15:34, Jim Abramson wrote: Can this be taken to mean that: - the practical maximum number of threads to run your single (non-ZEO) zope instance is {number of zodb connections in pool} else you risk deadlock You will want to make the connection pool a bit larger than the number

Re: [Zope] high loads, more threads, spinning wheels

2005-05-01 Thread Paul Winkler
On Sun, May 01, 2005 at 01:34:08PM +0200, Stefan H. Holek wrote: And there is nothing wrong with ZEO, really, there's only advantages. One potentially large quibble: If you have big (multi-megabyte) blobs in your ZODB, and this data is not cached in the client's ZEO cache, performance is an

Re: [Zope] high loads, more threads, spinning wheels

2005-04-30 Thread Jens Vagelpohl
Can this be taken to mean that: - the practical maximum number of threads to run your single (non-ZEO) zope instance is {number of zodb connections in pool} else you risk deadlock No, there should be more connections than threads, just as in the original configuration. if yes, would upping the

RE: [Zope] high loads, more threads, spinning wheels

2005-04-29 Thread Jim Abramson
Can this be taken to mean that: - the practical maximum number of threads to run your single (non-ZEO) zope instance is {number of zodb connections in pool} else you risk deadlock if yes, would upping the number of ZODB connections effectively raise the ceiling - e.g. 12 ZODB connections - 12

[Zope] high loads, more threads, spinning wheels

2005-04-25 Thread Tim Middleton
I've been doing some simple load tests on a zope application, and I've found when i increase the zserver-threads in zope.conf very much the zope server goes into some sort of cycle where it eats 100% cpu and refuses to any future requests until restarted. The load test is simply a small

Re: [Zope] high loads, more threads, spinning wheels

2005-04-25 Thread Florent Guillaume
Tim Middleton zope@zope.org wrote: I'm wondering if someone who knows the internals more might have some idea what's going on here. Or any tips on how to debug what zope is doing when it gets into this state. You can use DeadlockDebugger. Florent -- Florent Guillaume, Nuxeo (Paris,

Re: [Zope] high loads, more threads, spinning wheels

2005-04-25 Thread Jens Vagelpohl
On Apr 25, 2005, at 17:46, Tim Middleton wrote: I've been doing some simple load tests on a zope application, and I've found when i increase the zserver-threads in zope.conf very much the zope server goes into some sort of cycle where it eats 100% cpu and refuses to any future requests until

Re: [Zope] high loads, more threads, spinning wheels

2005-04-25 Thread Allen Schmidt
Which, BTW, is one of the coolest things ever! Still trying to figure out what it all means but it has really helped us to find things that were slowing us down. THANKS THANKS THANKS to Florent!! Allen Florent Guillaume wrote: Tim Middleton zope@zope.org wrote: I'm wondering if someone who