Re: Memory consumption of PyDS

Georg Bauer wrote:
> Hmm. It does grow a bit - but not that fast. I have it running since 
> 4.4.2004 and it now uses 78MB, with an RSS of 21MB. But that's a very 
> big installation - the one that renders http://hugo.muensterland.org/. 
> Another one that renders http://f-2.org/ is still at 48MB with 9MB RSS 
> and that one is running since Feb, 25th ...

If you want to debug this, I'd recommend whipping up a little tool that 
when poked, runs gc.collect then dumps the output of gc.get_objects out 
to the HTML. You'll have a lot to wade through, but odds are, if there 
is a memory leak, you'll see tons upon tons of one particular item that 
stands out, especially if you've run this for a while.

I'm no longer in a position to run pyds for days at a time due to 
changes in my computer set up, so I can't really help much with this.

I can say that I've recently had reason to distrust the Python garbage 
collector, at least in 2.3.3, but I have not taken the time to isolate 
the issue and see if it's a genuine bug or a flaw in my understanding of 
how it works... but I'm about 95% sure I was able to create a bona-fide 
memory leak in pure Python. However, I was playing with weakrefs and 
circular structures which almost certain exacerbated the problem; PyDS 
doesn't use weakrefs so I would hope this wouldn't apply.