I am seeing a large amounts of these 2005-08-31T08:40:18 INFO(0) ZSS:528/10.110.110.12:50602 Transaction blocked waiting for storage. Clients waiting: 1. 2005-08-31T08:40:18 INFO(0) ZSS:528/10.110.110.23:49161 Blocked transaction restarted. 2005-08-31T09:05:21 INFO(0) ZSS:528/10.110.110.23:49161 Transaction blocked waiting for storage. Clients waiting: 1. 2005-08-31T09:05:22 INFO(0) ZSS:528/10.110.110.12:50602 Blocked transaction restarted. 2005-08-31T10:18:26 INFO(0) ZSS:528/10.110.110.23:49161 Transaction blocked waiting for storage. Clients waiting: 1. 2005-08-31T10:18:28 INFO(0) ZSS:528/10.110.110.12:50602 Blocked transaction restarted. 2005-08-31T10:59:08 INFO(0) ZSS:528/10.110.110.23:49161 Transaction blocked waiting for storage. Clients waiting: 1. 2005-08-31T10:59:17 INFO(0) ZSS:528/10.110.110.12:50602 Blocked transaction restarted. 2005-08-31T10:59:31 INFO(0) ZSS:528/10.110.110.22:49161 Transaction blocked waiting for storage. Clients waiting: 1. 2005-08-31T11:00:13 INFO(0) ZSS:528/10.110.110.12:50602 Blocked transaction restarted. 2005-08-31T11:00:15 INFO(0) ZSS:528/10.110.110.23:49161 Transaction blocked waiting for storage. Clients waiting: 1. 2005-08-31T11:00:16 INFO(0) ZSS:528/10.110.110.22:49161 Transaction blocked waiting for storage. Clients waiting: 2. -----Original Message----- From: zope-bounces@zope.org [mailto:zope-bounces@zope.org] On Behalf Of zope-request@zope.org Sent: Thursday, September 01, 2005 12:00 PM To: zope@zope.org Subject: Zope Digest, Vol 16, Issue 2 Send Zope mailing list submissions to zope@zope.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.zope.org/mailman/listinfo/zope or, via email, send a message with subject or body 'help' to zope-request@zope.org You can reach the person managing the list at zope-owner@zope.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Zope digest..." Today's Topics: 1. Re: Zope scalabilty and problems (Sascha Ottolski) ---------------------------------------------------------------------- Message: 1 Date: Thu, 1 Sep 2005 16:45:11 +0200 From: Sascha Ottolski <sascha.ottolski@gallileus.de> Subject: Re: [Zope] Zope scalabilty and problems To: zope@zope.org Message-ID: <200509011645.12601.sascha.ottolski@gallileus.de> Content-Type: text/plain; charset="windows-1252" Am Mittwoch, 31. August 2005 18:50 schrieb J Cameron Cooper:

There are lots of ways to improve performance just administratively. You can improve various zope.conf settings, and set up caching (either RAM or HTTP Accel.) in Plone. You can also put a caching proxy server (like Squid) in front of your Zopes.

not to forget that playing with the zeo and/or zope database caches might help; if you see lots of conflict errors in you logs, may be an upgrade to 2.8 with MVCC does a benefit. and, of course, look carefully if any other tasks on all of your servers compete with your cpu and io resources. Cheers, Sascha P.S. just in case, debug mode or profiling and such are better to be disabled on your live system...:-) ------------------------------ _______________________________________________ Zope maillist - Zope@zope.org End of Zope Digest, Vol 16, Issue 2 ***********************************