> It looks like your application has a single persistent instance -- the
> root ExtendedTupleTable -- so there's no way for ZODB to manage the
> memory. That object and everything reachable from it must be in memory
> at all times.
Indeed, I tried running this program under ZODB 3.4b1 on Windows, and
about 4% of the way done it dies during one of the subtransaction
commits, with a StackError: the object is so sprawling that a
megabyte C stack is blown by recursion while trying to serialize it.
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org