[ZODB-Dev] State of persistent cache after commit
Rad Widmer
rwidmer at eclypse.org
Wed Oct 20 11:30:50 EDT 2004
It is my understanding that the persistent object cache is invalidated after a commit. Is there a
way to prevent this from occurring? If so, is there a downside to doing so? Memory usage is not a
big issue for me right now. In my application, I typically load a large number (> 100,000) of small
objects, then modify a small number of these. After a commit, I typically see long delays because
many objects need to be reloaded.
I'm running ZODB 3.3.0c1.
Thanks in advance,
Rad Widmer
More information about the ZODB-Dev
mailing list