ZEO 5.0.0b0 released

Jim Fulton <[email protected]>
Newsgroups gmane.comp.web.zope.zodb
Message-ID <CAPDm-FiaRtg36MFw_JjvjTGnRry=bQB8Jrn16c5FaDa7Sp86ng@mail.gmail.com>
ZEO 5.0.0b0 has been released.  This is a major revision of ZEO built on
the Python asyncio library rather than the ancient asyncore library.

Changes in this release as well as earlier ZEO 5 releases can be found here:

https://pypi.python.org/pypi/ZEO#b0-2016-08-18

I performed some performance tests:

https://docs.google.com/spreadsheets/d/1bTxtO9J7fcrGeZLaam38ncIEgWcXu
8Gpb-R8MfBhuYc/edit?usp=sharing

Here's my high-level summary of the results.

On Python 2.7, ZEO 5 is generally faster writing and slower reading than
ZEO 4.  When ZEO 5 prefetch is used, then it may be faster reading than ZEO
4.

On Python 3.5 using uvloop, ZEO 5 is faster that ZEO 4, sometimes much
faster, especially with more clients.

Using SSL slows down transactions by roughly 20% (it varies).

Using server sync slows down transactions a bit more. The transactions in
the tests were pretty small.  The impact of server sync would be less for
larger transactions.  With server sync, the client makes a do-nothing
request to the server at the start of a transaction to make sure it's seen
any invalidations that were in-flight when the transaction was initiated.
This is useful, for example, when you make a change using one client and
perform a transaction in a different client that depends on the change.
Server sync is somewhat similar to the polling done by Relstorage at the
start of a transaction.

ZEO 5.0 clients will work with ZEO 4.2 and later servers.  ZEO 5 servers
work with ZEO 5 clients.

Jim

-- 
Jim Fulton
http://jimfulton.info

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.