Dieter Maurer wrote:
A new proposal:
http://www.zope.org/Wikis/ZODB/MemorySizeLimitedCache
It outlines how to implement a ZODB cache limited not be the
number of containing objects but by their estimated memory size.
Feedback welcome -- either here or in the Wiki.
I think any work in this area can only be a good thing :-)
I like the idea of an interface allowing alternate cache
implementations, but will it suffer from not knowing what other possible
implementations could need or is this a really well defined boundary anyway?
I also really like the idea of a memory-limited cache, especially if
that limit is applied during a transaction rather than just at the
boundaries.
Is there a performance hit for using the pickle size? I guess I'm asking
if we have to pick the object to find it's pickle size?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev
