Re: [ZODB-Dev] two level cache

2007-03-29 Thread Dieter Maurer
Atmasamarpan Novy wrote at 2007-3-28 11:02 +0200: > ... >Problem: >Current ZODB design creates a separate cache for each ZODB connection >(ie. a thread in zope). It means that the same object could be >replicated in each connection cache. We cannot do much about it since we >do not know in advan

Re: [ZODB-Dev] two level cache

2007-03-28 Thread Benji York
Atmasamarpan Novy wrote: A current ZODB cache will become a first level cache (L1), each ZODB connection maintains its own copy. When an object is needed it reads it from L2 cache instead from a storage. L2 cache is a common for all ZODB connections. Objects are stored there in the state where

Re: [ZODB-Dev] two level cache

2007-03-28 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28 Mar 2007, at 11:02, Atmasamarpan Novy wrote: Two level cache: A current ZODB cache will become a first level cache (L1), each ZODB connection maintains its own copy. When an object is needed it reads it from L2 cache instead from a storage

[ZODB-Dev] two level cache

2007-03-28 Thread Atmasamarpan Novy
Hi, I certainly do not know much about ZODB internals, therefore I do not know if this idea make much sense. But it has been bothering me for some time. Problem: Current ZODB design creates a separate cache for each ZODB connection (ie. a thread in zope). It means that the same object could