Hello people
Thank you for all your answers and comments!
Unfortunately I can't test your advices right now because of other urgent
[as always :-( ] businesses.
I'll do it as soon as i'll be able.
Thanx a lot!!!
Mike Andreev
Ged Haywood wrote:
I'd suggest setting MaxRequestsPerChild to a low value (I generally
use something in the range of 50-100 but Perrin will tell you that's
*very* low... :) to avoid leak problems.
A setting of 0 is fine, as long as you are using Apache::SizeLimit or
Apache::GTopLimit. In
Hello.
I develop now my first project on mod_perl.
When we started to test this project on separate server we faced excess opened
files limit problem. There are no other serious tasks on this server, only
mysql with project databases and apache. During the work with web interface
number of
On Thu, 2002-04-04 at 00:46, Mike V. Andreev wrote:
Hello.
hi.
During the work with web interface
number of open files slowly grows and finally reaches OS limit.
And this happens with only 2-3 users working with interface !!!
If to restart apache number of open files comes back in norm,
Hi there,
On Wed, 3 Apr 2002, Mike V. Andreev wrote:
files limit problem.
httpd.conf:
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
MinSpareServers 5
MaxSpareServers 10
StartServers 5
MaxRequestsPerChild 0
MaxClients?
What kind of diagnostics can be done to find out
Hi again,
On Thu, 4 Apr 2002, Mike V. Andreev wrote:
MaxRequestsPerChild 0 -- if I set this limit to 10 then the problem disappear
but that way deprives project of mod_perl usage advantages
Not at all, for example 90 percent of your requests won't have to
reload Perl. (Of course they won't
