-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote: > On Wed, Apr 7, 2010 at 1:39 PM, Andreas Jung <li...@zopyx.com> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> According to the ZODB 3.10 release notes we will have dedicated >> processes on the ZEO server side for each client connection. > > Where do they say that? > > They say that "ZEO clients now work in forked processes." Is that what > you're referring to? That should probably have been worded > differently: "ZEO clients now work properly in forked processes."
I had multi-threading in my mind but now was reading about forked processed...that's confused me. > >> Our typical scenario is like this: we run 5-6 ZEO servers where each >> server manages one fat storage (50-100GB). Roughly 20-30 ZEO clients are >> connected to each ZEO server (10 ZEO clients with 2-3 works threads >> each) doing reads and writes plus a certain number (perhaps 5-10) ZEO >> clients doing mass export/read operations. Should we see any benefits >> from using a ZODB 3.10 server in such a scenario? > Better performance in terms of higher throughput and increased number of load operations (which is essential to the reading batch clients)? Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAku8yGkACgkQCJIWIbr9KYyXbwCgsngpGlbcOWrnGdDJKbORhfCh clwAn36Xoso5B8OE/MV3jcMMMkeJQjOa =irmP -----END PGP SIGNATURE-----
_______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev