[Zope-dev] How is memory shared between Zope threads?

Hello all, I have noticed incosistencies between Zope threads when objects change. It appears that some threads see the new image of the object while others see the old image. Can anyone enlighten me on how Zope ensures that all threads are seeing the same images? Or at least point me to the

[Zope-dev] Increased system CPU cycles under heavy load?

Hello all, I apologize if this might be more appropriate for a Linux list. From our time-series graphs, we are noticing that the percentage of CPU cycles spent on 'system' tasks grows considerably under heavy load. Does anyone know what kinds of operations fall under 'system'? Task switching,

Re: [Zope-dev] How is memory shared between Zope threads?

"R. David Murray" wrote: On Thu, 1 Mar 2001, Erik Stephens wrote: Naively, I can think of 2 approaches: a shared memory approach or a separate memory per thread with notifications. Zope behaves like each thread as its own copy of in-memory pieces and sometimes these per/thr

[Zope-dev] DB connection pooling

Hello all, I've been working on an implementation of connection pooling for the MySQLDA. Basically, Zope connections will be pooled by connection string to reduce the number of unecessary connections to MySQL. The number of connections will be reduced in 2 respects: 1) Multiple threads will

Re: [Zope-dev] DB connection pooling

Dieter Maurer wrote: Erik Stephens writes: I've been working on an implementation of connection pooling for the MySQLDA. Basically, Zope connections will be pooled by connection string to reduce the number of unecessary connections to MySQL. Isn't that trivial with Zope (thanks

[Zope-dev] Running out of options

Hello, This is regarding the Zope restarting problem that's been talked about recently. We've tried TONS of different configurations: Python 2.1.x (with threads and with without pymalloc) Zope 2.4.x (built wo_pcgi binary installs) ZMySQLDA (with without the Kromer patch) MySQLdb