Make sure the MaxClients & MaxRequestsPerChild is set low enough
so that your machine doesn't start swapping excessively. Try
a benchmark against your system with "ab -c 100 -n 10000 modperl-URL"
and see what happens. If your MaxClients is 100 and MaxRequests 100,
this will be a decent test against your system. Fire up top
and watch the fun! Note to get a real life load test, you will
need to test against a mix of URLs, not just one, but you'll get
the idea if you hit a RAM heavy URL, like one database driven.
--Joshua
> Frédéric Schwien wrote:
>
> Hi,
>
> i'am encouring problems with a machine that is hosting several completly independant
>modperl featured host.
> It is crashing without any apparent reason (nothing in the logs), and it seems to be
>a lack of memory (1 GB !). The only visual aspect is that it
> becomes impossible to login in via ssh after it has crashed. The reboot is necessary
>!!!
>
> My configuration is
> Linux 2.2.14,
> 1GB Memory,
> apache 1.3.12
> modperl 1.24
> Perl 5.6
>
> There is no significant traffic over run due to the new sites added using modperl.
> At the begining, it was running 3 virtualhosts, everything was working fine for
>months !
> As soon as I added 3 new virtualhosts, it starting crashing 2 or 3 times a week. I
>removed some of them that were not vital, and then it is crashing
> once a week .
>
> The httpd process is only 12 Mb big, I do not think it is too heavy , is it ?
>
> Is anybody having any advice ? I'm running out of ideas ...
>
>
> THanks a lot
>
>
> Fred
>
