On Aug 9, 2005, at 7:01 AM, Sascha Ottolski wrote:
What we've seen so far: we used to set the cache-size to 250 MB;
and every
know and than we have to observe that after a restart of a client a
cache
verification is necessary (while not always obvious, why this
happened),
which often takes
Am Dienstag, 9. August 2005 02:03 schrieb Andrew Langmead:
> (on these
> machines, the ZEO client cache is set to 2GB and a cache flip occurs
> maybe twice a week.)
I think this part to be quite interesting. We too are experimenting with the
optimal cache sizes, where our (daily) packed Data.
On Aug 8, 2005, at 10:01 AM, M. Krainer wrote:
So far our story, but what I really wonder is, if there's anyone out
there who has a similar large installation. Please let me know how
large your zope instance is and what you have done to increase your
(write) performance. Also any ideas that may h
--On 8. August 2005 16:01:13 +0200 "M. Krainer" <[EMAIL PROTECTED]>
wrote:
Hi!
We run a self developed zope product originally based on cmf but
highly customized and extended. Our Data.fs now has grown to a
(packed) size of > 25GB and we are running more and more into
performance troubles (
Do you mount your catalog in a separate database? If not, you may
want to try this to split up the conflict domains. Multiple catalogs
may or may not help. Multiple databases will help more likely, IMO.
Stefan
On 8. Aug 2005, at 16:01, M. Krainer wrote:
Currently we think that our bottle
I can't provide any specific advice but you may want to read the
"Scaling Zope" proposal that this points to:
http://www.plope.com/Members/chrism/scalingzope/view
Note that sessions are a frequent source of conflict errors. If you use
them, you may want to upgrade to Zope 2.8.1, which has MVCC f
Hi!
We run a self developed zope product originally based on cmf but
highly customized and extended. Our Data.fs now has grown to a
(packed) size of > 25GB and we are running more and more into
performance troubles (mostly due to a lot of conflict errors). Our
users make a lot of updates, i.e. we
