[ZODB-Dev] State of persistent cache after commit

[Rad Widmer]

Yes, thanks for the info. I was off-base with the invalidation theory, thanks for clearing that up. 
The default cache_size is the most likely cause of my performance problems. I did a quick check with 
a much larger cache_size (50,000) and the results look promising.

> 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.
>
>

Thanks for the help,

Rad Widmer