Hi Stas,
Batara, please try first with mod_perl 1.19_16 or the current cvs [1]. If it didn't make any different please tell us how much memory consumes each modperl process on the startup (shared and absolute). You can use Apache::VMonitor for that purpose if you have libgtop installed.
I tried mod_perl 1.19_16 with the same result.
But the problem is gone after I changed MaxRequetPerChild from 6000 to 1000. I guess the application just eats up too much memory. Thanks a lot :)
It's possible that your application leaks. In which case you need to fix that. The doc Perrin has pointed you to [1] should give you enough information on how to deal with that situation. You didn't answer my question about the sizes of the processes, so I can't give any further advice.
It's also possible that mod_perl 2 leaks, but w/o seeing a specific code that we can reproduce the problem with, we can't know. So if you think it's a mod_perl 2 problem, please shrink your code to the shortest possible version that you still see the leak with and post it here.
p.s. Instead of tuning MaxRequestPerChild it's much better to use Apache::SizeLimit and its friends. But at the moment it is not yet ported to mp2, so stay tuned for when its port is announced.
Thanks.
[1] http://perl.apache.org/docs/1.0/guide/performance.html
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
