On Apr 24, 2009, at 2:37 AM, Shane Hathaway wrote:
Christian Theune wrote:
On Thu, 2009-04-23 at 15:02 -0700, David Glick wrote:
Having now realized the folly of trying to split things into
multiple databases, I would really like to merge these 3
databases back into 1. Any ideas for
In ZODB 3.9, you can pack without doing garbage collection. This
should at least buy you time, if not solve your problem (depending on
how much garbage your application creates.
What about zc.FileStorage? Does this support packing w/o GC?
And does that work on versions of ZODB 3.9?
On Apr 27, 2009, at 8:57 AM, Alan Runyan wrote:
In ZODB 3.9, you can pack without doing garbage collection. This
should at least buy you time, if not solve your problem (depending on
how much garbage your application creates.
What about zc.FileStorage? Does this support packing w/o GC?
Attached is a minimally changed analyze.py file, it adds a min, max
size of class types.
Maybe someone can help me. We have a customer whose running out of memory.
We suspect it is content related, i.e. they uploaded a really big file
and in some way
the entire file is a single PData or some
David Glick wrote:
Taking the existing ExportImport.py code as a starting point, it looks
like I would need to:
1. modify the persistent_load method to handle rewriting extended
references of types 'n' and 'm'
2. provide some way to process several export files at once, and input
a
On 27.04.2009 15:13 Uhr, Jim Fulton wrote:
Note that ZODB 3.9 is pretty stable. We're using it in production. It
is alpha mainly because Shane and I are still sorting out integration
of RelStorage.
Speaking of ZODB 3.9 - when do you expect going beta (I know it's done
when it is done) since
