(Resending because I used the wrong From address and the mail got stuck
in moderation.)
Some goals, in order of decreasing priority
1. ZODB should work on Python 3
2. ZODB databases created on Python 2 should be loadable with ZODB on
Python 3.
3. ZODB databases created on Python 3 should
I'd be curious to know what your results are, whichever path you decide to
take! Might help inform me as to what might help on my server...
One thing I haven't yet understood is - how come the ZEO server itself
doesn't have a cache? It seems that would be a logical place to put one as
the ZEO
On Fri, Mar 8, 2013 at 2:17 PM, Claudiu Saftoiu csaft...@gmail.com wrote:
Once I know the difference I'll probably be able to answer this myself,
but I wonder why the ZEO server doesn't do the sort of caching that allow
the client to operate so quickly on the indices once they are loaded.
On Fri, Mar 8, 2013 at 12:31 PM, Leonardo Santagada santag...@gmail.comwrote:
On Fri, Mar 8, 2013 at 2:17 PM, Claudiu Saftoiu csaft...@gmail.comwrote:
Once I know the difference I'll probably be able to answer this myself,
but I wonder why the ZEO server doesn't do the sort of caching that
It would be great if there was a way to advise ZODB in advance that
certain objects would be required so it could fetch multiple object
states in a single request to the storage server.
I saw a ZODB prefetching discussion long time ago, but maybe the
authors themselves can weight in here
A very simple alternative to prefetching would be to load the whole DB
into memory indiscriminately, if it is configured to do so. This way,
you can store your catalog in a separate db and request all of it from
the ZEO server and cache it straight away.
I'm still partial to a memcached cache
On 03/07/2013 10:48 AM, jason.mad...@nextthought.com wrote:
On Mar 7, 2013, at 11:35, Sean Upton sdup...@gmail.com wrote:
On Thu, Mar 7, 2013 at 7:31 AM, jason.mad...@nextthought.com
wrote:
I only spotted two uses of this assumption in RelStrorage, the
above-mentioned `_prepare_tid`, plus
Hi there,
I've been discussing this issue with Laurence Rowe on the pylons-dev
mailing list, and he suggested bringing it up here.
I'm writing a MongoDB data manager for the python transaction package:
https://github.com/countvajhula/mongomorphism
I noticed that for a synchronizer, the
