-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14 Sep 2006, at 20:49, Brian Brinegar wrote:

One ZEO server can deal with multiple storages just fine.
Transactions involving multiple storages commit just fine.

Caveat: You buy nothing by having a single ZEO process serve several
ZODBs when you're trying to decrease commit times. You should run a
ZEO process per ZODB you're serving out, that way the writes can be
segregated and parallelized. That also makes it easier to move
processes/databases around disks/hosts to spread I/O load.

Just to clarify, you are saying that a single ZEO server would not be
able to deal with multiple storages simultaneously and that a
transaction in one storage would block transactions in all other storages.

ZEO server processes are single threaded, access to the databases must be serialized.


However, if we were to run multiple ZEO processes this would not be the
case?

Right.

jens



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFCk3ARAx5nvEhZLIRAr4zAJ9IsO1Hv1t1QxOgP8Hoq5pTZwyQCACfRpEO
fNmfNMHm2mhjhbTRPKt5pyY=
=SXPM
-----END PGP SIGNATURE-----
_______________________________________________
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 )

Reply via email to