I can't provide any specific advice but you may want to read the
"Scaling Zope" proposal that this points to:
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 for the
(eliminates read conflicts) for the storage that backs sessions by
Write operations are pretty hard to optimize away. One possible
optimization if your bottleneck really is the catalog is to use
a-QueueCatalog-based portal_catalog instead of a straight-ZCatalog-based
one. See http://cvs.zope.org/Products/QueueCatalog/ for more info.
On Mon, 2005-08-08 at 16:01 +0200, M. Krainer wrote:
> 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 have lots of write operations.
> Currently we think that our bottle neck is the 'portal_catalog' and
> I'm working on splitting it up into multiple ZCatalogs.
> 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 help us are welcome.
> Additional info:
> 4 ZEO clients, 1 ZEO server (all machines have dual P4 and 3-4GB ram),
> Zope maillist - Zope@zope.org
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://mail.zope.org/mailman/listinfo/zope-dev )
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -