On Fri, 2008-05-02 at 06:09 +0000, Max Kanat-Alexander wrote:
> Hmm. I just loaded the largest file in my repo, and loggerhead is only
> using 184MB. But when I killed it earlier today, it was using 641MB.
>
> The issue is that other services are running on this box. Is it just the
> nature of Python (similar to Perl) to never return memory to the system?
Older pythons had that behaviour, but it is largely fixed these days.
There are fundamental bugs in loggerhead but some progress is being
made; it will unfortunately change the runtime dependencies, as the
template engine is one of the culprits causing the bloat.
On Fri, 2008-05-02 at 06:09 +0000, Max Kanat-Alexander wrote:
> Hmm. I just loaded the largest file in my repo, and loggerhead is only
> using 184MB. But when I killed it earlier today, it was using 641MB.
>
> The issue is that other services are running on this box. Is it just the
> nature of Python (similar to Perl) to never return memory to the system?
Older pythons had that behaviour, but it is largely fixed these days.
There are fundamental bugs in loggerhead but some progress is being
made; it will unfortunately change the runtime dependencies, as the
template engine is one of the culprits causing the bloat.
-Rob www.robertcolli ns.net/ keys.txt>.
--
GPG key available at: <http://