On Mon, 2003-10-13 at 11:02, Kyle Dawkins wrote:
> You must, at ALL times, keep your machine from swapping out Apache
> children.
Good advice. To go a step firther, this is all covered in detail in the
mod_perl documentation here:
http://perl.apache.org/docs/1.0/guide/performance.html#Performance
Mike
I'm pretty sure you're experiencing a standard problem that most of us have been bitten by at one stage or another. Ged is right when he says that 120 apache children at 40MB a pop will eat your RAM up. The piece of the puzzle that you're missing is this: due to the dopey VM code in Linux,
Ged,
>Do you have a single mod_perl server setup? If you have mod_perl
>scripts both serving static documents and waiting on Oracle you might
>want to investigate using a light/heavy server approach. A front-end
>(Apache only) server accepts all requests, and passes those that need
>Perl to the
Hi there,
On Mon, 13 Oct 2003, Mike Norton wrote:
> we have set the MaxClients to 120 Clients and also set the
> MaxRequestsPerChild to 100 to try to resolve this problem however it
> still occurs under these conditions. The largest process is about
> 40M (4MB shared)
If you have 120 clients eac
2003 13:57
To: Mike Norton
Cc: [EMAIL PROTECTED]
Subject: Re: Swapping
Hi there,
On Mon, 13 Oct 2003, Mike Norton wrote:
> [snip] under a heavy load it all of a sudden consumes a large amount
> of swap and the server load shoots through the roof [snip] Does
> anyone have any ideas
Hi there,
On Mon, 13 Oct 2003, Mike Norton wrote:
> [snip] under a heavy load it all of a sudden consumes a large amount
> of swap and the server load shoots through the roof [snip] Does
> anyone have any ideas on how to resolve this issue or why it happens
No idea why it happens, you haven't gi
