Hi,
I had the same prob and lowering maxrequestsperchild helped.
Are there possibilities to clean up the used mem on end of the
mod_perl-script manually? Or have I always set maxrequestsperchild to lower
values? If it?s possible to do it by myself, what means the overhead of
creating a new apache-thread in opposite of it in the manual clean-up?
Matthias
-----Ursprungliche Nachricht-----
Von: Ged Haywood [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 28. Mai 2001 20:08
An: Antonios Christofides
Cc: [EMAIL PROTECTED]
Betreff: Re: Memory leak
Hi there,
On Mon, 28 May 2001, Antonios Christofides wrote:
> script offers database search facilities on the web. If a search is
> performed which results in many (namely 400) rows being returned, then
> the httpd child that serves the request grows by 2 MB. Have a child
> serve that request ten times, and its size will grow from an initial 8
> MB to 28 MB. Another ten times and it will go to around 50 MB.
If a row is around 5kbytes then I don't think it's a Perl/mod_perl
problem, I think you're keeping your variables hanging around in memory.
Don't forget that when you use mod_perl the interpreter doesn't exit,
so a lot of memory cleanup which happens at exit doesn't happen under
mod_perl. What happens if you set maxrequestsperchild to ten?
73,
Ged.
