I found it !!!
Issueing an apachectl restart (or kill -HUP) make the apache parent
process size grow !
This is the case on all of our FreeBSD boxes. I can't reproduce it on Linux.
Take a look at this:
apachectl start
# ps
Len Kranendonk wrote:
Philip, as you're using FreeBSD too, could you confirm this ?
vegeta# apachectl start
vegeta# ps -aux | grep httpd | grep root
USERPID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 50770 7.5 2.7 16828 14180 ?? Ss 10:55AM 0:00.30 httpd
On Tue, 2006-01-03 at 16:46 +0100, Len Kranendonk wrote:
I found it !!!
Issueing an apachectl restart (or kill -HUP) make the apache parent
process size grow !
This was a well-known issue with mod_perl 1.x built using DSO. I never
use graceful restart because of this. I thought 2.x got
Perrin Harkins wrote:
On Tue, 2006-01-03 at 16:46 +0100, Len Kranendonk wrote:
I found it !!!
Issueing an apachectl restart (or kill -HUP) make the apache parent
process size grow !
This was a well-known issue with mod_perl 1.x built using DSO. I never
use graceful restart because of this.
Issueing an apachectl restart (or kill -HUP) make the apache parent
process size grow !
This was a well-known issue with mod_perl 1.x built using DSO. I never
use graceful restart because of this. I thought 2.x got rid of this
issue though. You could try making a static build and see if
Tyler MacDonald wrote:
Interesting... I just chatted with Brian Somers (resident freeBSD
guru) and he told me that he was getting the same problem under a
normal perl, but when he recompiled his perl to use FreeBSD's malloc
(rather than perl's own), the problem went away; he could restart
On Jan 3, 2006, at 10:29 AM, Philip M. Gollucci wrote:
-Dusemymalloc=y is the default for lang/perl5.8
Also, the previous example had this same setting.
I'll try a manual compile with it off at some point.
FWIW, I found that turning off Perl's malloc() prevented segfaults in
mod_perl 1 on
I'll try a manual compile with it off at some point.
./Configure -sde \
-Uinstallusrbinperl \
-Dcc=cc \
-Doptimize=-g3 -O0 \
-Duseshrplib \
-Dusethreads=n \
= -Dusemymalloc=n \
-Duse64bitint \
-Dccflags=-pipe \
-Ud_dosuid \
-Ui_gdbm \
-Ui_malloc \
-Ui_iconv \
Hello all,
I'm running Apache/2.0.54,mod_perl/2.0.1,
Perl/v5.8.7 on FreeBSD 6.0.
Right after starting apache (with preloading the
needed perl modules) the httpd root process is about 40MB.
After several days it has grown to over
100MB.
I'm using Apache2::SizeLimit to kill of httpd
Happy2006 everyone,
I'm running Apache/2.0.54,mod_perl/2.0.1,
Perl/v5.8.7 on FreeBSD 6.0.
Right after starting apache (with preloading the
needed perl modules) the httpd root process is about 40MB.
After several days it has grown to over
100MB.
I'm using Apache2::SizeLimit to kill of
On Mon, 2 Jan 2006 20:34:42 +0100
Len Kranendonk [EMAIL PROTECTED] wrote:
Happy 2006 everyone,
I'm running Apache/2.0.54, mod_perl/2.0.1, Perl/v5.8.7 on FreeBSD
6.0.
Right after starting apache (with preloading the needed perl modules)
the httpd root process is about 40MB. After several
On Mon, 2006-01-02 at 20:34 +0100, Len Kranendonk wrote:
Right after starting apache (with preloading the needed perl modules)
the httpd root process is about 40MB.
After several days it has grown to over 100MB.
How are you measuring this?
My understanding is that the parent process is not
Do you have any globals or other shared information that grows very
large? Do you read in any large data sets either from a database or
a file into the application all at once?
We're using a global %session hash, which is undef 'fed when the session is
closed.
I'm not reading in large data
On Mon, 2006-01-02 at 21:48 +0100, Len Kranendonk wrote:
We're using a global %session hash, which is undef 'fed when the session is
closed.
I'm not reading in large data sets, but even if I did that should grow the
child process,
not the parent process, right ?
Right.
The application
How are you measuring this?
top, or ps aux and watch the RSS column (the real memory (resident set)
size of the process (in 1024 byte units)).
A sample top output:
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
87075 www40 178M 174M accept 0:32
Perrin Harkins wrote:
On Mon, 2006-01-02 at 21:48 +0100, Len Kranendonk wrote:
We're using a global %session hash, which is undef 'fed when the session is
closed.
I'm not reading in large data sets, but even if I did that should grow the
child process,
not the parent process, right ?
Right.
Are you using IPC::SharedCache for your HTML::Template caching?
No, I'm using the file_cache=1 option, which uses Storable (I believe).
This doesn't really help you, but I don't notice the parent growing on
any of my FreeBSD boxes doing a variety of things.
So, most likely I'm doing something that you don't do
Are you using ModPerl::Registry, because I still do.
On Mon, 2 Jan 2006, Len Kranendonk wrote:
I'm running Apache/2.0.54, mod_perl/2.0.1, Perl/v5.8.7 on FreeBSD 6.0.
Right after starting apache (with preloading the needed perl modules) the
httpd root process is about 40MB.
After several days it has grown to over 100MB.
what would be
i recently made a memory bench with a self-compiled apache 1.33 that
showed that every request (of a mod_perl-handler that just outputs
content-type) added a small amount of memory to the child process; i
haven't watched the parent process, though.
That would imply a memory leak .
--
On Mon, 2006-01-02 at 22:04 +0100, Len Kranendonk wrote:
How are you measuring this?
top, or ps aux and watch the RSS column (the real memory (resident set)
size of the process (in 1024 byte units)).
Okay, my other guess then is that your parent process really uses this
much memory at
21 matches
Mail list logo
