[ZODB-Dev] State of persistent cache after commit

[Christian Robottom Reis]

On Wed, Oct 20, 2004 at 02:32:32PM -0400, Tim Peters wrote:
> I'll guess, though:  one thing that happens after a commit is that an LRU
> cache-eviction pass is run, to reduce the database connection's in-memory
> cache to its configured size.  That's got nothing to do with invalidation,
> but will ghostify objects even if they've merely been read.
> 
> > I'm running ZODB 3.3.0c1.
> 
> Try playing with the DB constructor's optional cache_size argument.  It
> defaults to 400, meaning that a cache-eviction pass will try to boot out all
> but 400 objects.  That fits the symptoms you describe.  DB instances also
> have getCacheSize() and setCacheSize(new_cache_size) methods.

Interesting. This is something that could be done for both ZEO client
and server, which beckons the question: is it useful in both situations,
or is this a client-side only issue?

Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331