Gary Poster wrote:
you can call cache minimize after a threshold.. maybe every 100
iterations.
sounds good, assuming you know you are not writing.
Fantastic! My scripts are running without fail now (I used to have to
change them to pick up where they left off and re-run about four
Gary Poster wrote:
you can call cache minimize after a threshold.. maybe every 100
iterations.
sounds good, assuming you know you are not writing.
I've used this trick loads, especially for huge datastructure migrations
where writing is happening. I wonder why I haven't bumped into
On Aug 2, 2007, at 7:51 AM, Chris Withers wrote:
Gary Poster wrote:
you can call cache minimize after a threshold.. maybe every 100
iterations.
sounds good, assuming you know you are not writing.
I've used this trick loads, especially for huge datastructure
migrations where writing is
On Aug 2, 2007, at 9:33 AM, Jim Fulton wrote:
On Aug 2, 2007, at 7:51 AM, Chris Withers wrote:
Gary Poster wrote:
you can call cache minimize after a threshold.. maybe every 100
iterations.
sounds good, assuming you know you are not writing.
I've used this trick loads, especially for
snip...
line 96, in
__setstate__
Persistent.__setstate__(self, state)
MemoryError
means you have run out of memory. check your jail or how much memory
you have allocated.
you can call cache minimize after a threshold.. maybe every 100 iterations.
there are finer grain mechanisms to do
