Here's my setup using ZEO/ZRS: zserver-threads 6 <zodb_db main> mount-point / # ZODB cache, in number of objects cache-size 20000 pool-size 10 <zeoclient> server hostname1:port1 server hostname2:port2 read-only-fallback true storage 1 name zeostorage var $INSTANCE/var # ZEO client cache, in bytes cache-size 100MB # Uncomment to have a persistent disk cache #client zeo1 </zeoclient> </zodb_db> J.F. -----Original Message----- From: zope-bounces@zope.org [mailto:zope-bounces@zope.org] On Behalf Of Brian Sullivan Sent: January 16, 2007 11:02 AM To: Zope Users Subject: Re: [Zope] Re: pool_size On 1/16/07, Doyon, Jean-Francois <jdoyon@nrcan.gc.ca> wrote:
Here's what I think I know (though I could be wrong):
- The pool size is the number of ZODB connections maintained. - It should be at least as high as the number of zserver threads + 1 I
think? - I use zserver threads 6 and pool_size 10, works fine. - zserver threads is basically a measure of how many concurrent requests you want your server to be able to handle, by default, it's 4
(and pool size 7 IIRC?). - The downside is you have to balance this with the cache size, since the cache size is per thread ... So your RAM usage could go up significantly.
Useful info -- I see a config setting for zserver-threads but how do you set the pool_size ? -- in the zope.conf? How? _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )