Thanks for your quick reply!
So, the best place to call those would be during my commit break (whenever I
decide to take it? [which would be less often if I could be sure of no
crashing]). Are there any other problems with the way I was using ZODB in
my code? I really like it, but I recognize that it's a lot more complicated
than my old system.
On Mon, May 10, 2010 at 12:48 PM, Alan Runyan <runy...@gmail.com> wrote:
> > The DB on the choked process is perfectly good up to the last commit when
> > choked, and I've even tried extremely small values of cache_size_bytes
> > cache_size, just to see if I can get it to stop allocating memory and
> > nothing seems to work. I've also used string values ('128mb') for
> > cache-size-bytes, etc.
> On the connection object there are two methods you want to use:
> - cacheMinimize
> This is more of a heavy hand which attempts to deactive *all* non
> modified objects from cache.
> - cacheGC
> This will clean up the internal cache via the cache-byte-size parameter.
> If you are not calling these (I do not believe they are called in
> in your code; then they are probably not being called.
Stanford Computer Science
BS '09, MS '10
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org