www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From George Michaelson <...@dstc.edu.au>
Subject general/4463: some httpd have extremely large memory footprints, 10x the norm
Date Mon, 24 May 1999 02:03:44 GMT

>Number:         4463
>Category:       general
>Synopsis:       some httpd have extremely large memory footprints, 10x the norm
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun May 23 19:10:02 PDT 1999
>Originator:     ggm@dstc.edu.au
>Release:        1.3.4
Solaris 2.6, gcc 2.8.1
SunOS mirror.aarnet.edu.au 5.6 Generic_105181-13 sun4d sparc SUNW,SPARCserver-1000

the host in question is a large FTP/www mirror and provides access to
files such as RedHat ISO images, StarOffice as http protocol downloads as
well as FTP.

we see random (unknown) instances of httpd where the memory footprint grows
to be 20-30Mb, with 10+ Resident. kill -HUP clears.

After kill -HUP the machine stops swapping. /tmp is in swap, we then also
see an end to "out of /tmp" space problems.

top and vmstat and ps agree about the process size

Without having looked in any depth, I wonder if use of a mmap() form of I/O
is leading to large objects getting mapped into the server memory space and
then not getting released.

setting the number of calls before child-death down reduces the problem so
we have a workaround.

I did search manual pages but found no reference to directives which seem to
address potential memory growth issues.

[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

View raw message