> >at each level of recursion. What seems to be the case though is that when we
> >start going bac
> >up the stack that memory doesn't seem to be released at each pop. If, say,
> >at max depth
> >500mb of ram has been allocated I don't see that released at any point
> >except for when
> >perl exits and then of course it is all released at once. Or at least that
> >is what
> >seems to happen.
>
> Perl doesn't release memory, it keeps it for reallocation.
> This is (was?) one of the issues one had to be aware of with mod_perl.
Ah! Ok, so maybe I was confused about this. Even if I set the last reference to
an object to undef perl
will keep the memory until exit? The high water mark for memory usage never
goes down?
Well, that is fine I suppose, it isn't like this process will be really all
that long lived.
It also means that the iterative form of this algorithm will use all that much
less ram, I think.
_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm
