Hello Tres,
thanks for your detailed answers!
Am 12.04.2010, 22:42 Uhr, schrieb Tres Seaver tsea...@palladion.com:
Additionally I made some quick performance tests. I committed 1kb sized
objects and I can do about 40 transaction/s if one object is changed per
transaction. For 100kb objects
40 tps sounds low: are you pushing blob content over the wire somehow?
I have seen the ZEO storage committing transactions at least an order of
magnitude faster than that (e.g., when processing incoming newswire
feeds). I would guess that there could have been some other latencies
involved in
Running your test script on my small amazon EC2 instance on linux
takes between 0.0 and 0.04 seconds (I had to remove the divide by
total to avoid a zero division error). 0.02 is 5000/s.
Laurence
On 14 April 2010 00:25, Nitro ni...@dr-code.org wrote:
40 tps sounds low: are you pushing blob
Am 14.04.2010, 04:08 Uhr, schrieb Laurence Rowe l...@lrowe.co.uk:
Running your test script on my small amazon EC2 instance on linux
takes between 0.0 and 0.04 seconds (I had to remove the divide by
total to avoid a zero division error). 0.02 is 5000/s.
Thanks for running the test.
Intrigued
[Nitro]
...
I wonder if _commit is really *that* slow
Six years ago I timed factor-of-100 speed differences due to using MS
_commit() on WinXP at the time:
https://mail.zope.org/pipermail/zodb-dev/2004-July/007720.html
or if there's another (faster) function which can be called...
No MS
For the record, with
import os
os.fsync = lambda fd: 0
at the top of the test app I get ~3700 tx/s.
-Matthias
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
