[mailto:[EMAIL PROTECTED]
Sent: Saturday, January 12, 2008 4:59 AM
To: users@httpd.apache.org
Cc: Graham Frank
Subject: Re: [EMAIL PROTECTED] RSS of Apache Processes
On Sat 12 Jan 2008, Graham Frank wrote:
> Correct me if I'm wrong, but should RLimitMem help prevent the RSS value
>
&g
On Sat 12 Jan 2008, Graham Frank wrote:
> Correct me if I'm wrong, but should RLimitMem help prevent the RSS value
>
> >from going insane? I disabled my Perl script on one of the web servers
>
> today, and after 11 hours each process got up to a RSS of 550MB each.
http://httpd.apache.org/docs/2.2
er of the Better Business Bureau
-Original Message-
From: Graham Frank [mailto:[EMAIL PROTECTED]
Sent: Friday, January 11, 2008 7:18 AM
To: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] RSS of Apache Processes
Hi,
It looks like that's the case, yes.
Graham Frank
e.org
Subject: Re: [EMAIL PROTECTED] RSS of Apache Processes
On Jan 10, 2008 9:23 PM, Graham Frank <[EMAIL PROTECTED]> wrote:
> Also,
>
> If it were a memory leak, as it appears to be, why do the new processes
> immediately go to the high RSS values?
Does the rss of the parent p
On Jan 10, 2008 9:23 PM, Graham Frank <[EMAIL PROTECTED]> wrote:
> Also,
>
> If it were a memory leak, as it appears to be, why do the new processes
> immediately go to the high RSS values?
Does the rss of the parent process increase as well? That would
explain the high rss in new children.
--
On Jan 11, 2008 3:23 AM, Graham Frank <[EMAIL PROTECTED]> wrote:
> Also,
>
> If it were a memory leak, as it appears to be, why do the new processes
> immediately go to the high RSS values?
Let me guess: Some of the memory include in the RSS value is actually
memory that is shared by all processes
On Thu, Jan 10, 2008 at 08:18:54PM -0600, Graham Frank wrote:
> We actually have the MaxRequestsPerChild set to 1000 and KeepAlive off.
That means the leak is more than 100KB per request on average, although
it could be one very bad leak :/
> Know of any way that we could find the leak considerin
PROTECTED]
Subject: RE: [EMAIL PROTECTED] RSS of Apache Processes
Hey,
We actually have the MaxRequestsPerChild set to 1000 and KeepAlive off.
Know of any way that we could find the leak considering the vastness of all
the possibilities?
Thanks.
Graham Frank
Neoservers LLC - Founder and Owner
Ph
-Original Message-
From: Colm MacCarthaigh [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 10, 2008 8:10 PM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] RSS of Apache Processes
On Thu, Jan 10, 2008 at 07:36:19PM -0600, Graham Frank wrote:
> Can anyone offer up an explanat
On Thu, Jan 10, 2008 at 07:36:19PM -0600, Graham Frank wrote:
> Can anyone offer up an explanation for this? Thanks.
Everything you describe is incredibly normal behaviour associated with a
memory leak :-) You can also set a maximum number of requests per child
to alleviate the problem.
Of cours
Hello All,
I have three web servers which periodically crash due to Apache using up all
of the RAM on the server. No matter how much RAM we put in, it always
happens. Currently, there's 16GB of RAM on each server running Linux
x86_64.
Watching top, and the RSS of the Apache processes cons
11 matches
Mail list logo
