On Thu, Oct 19, 2000 at 01:55:50PM -0400, Philippe M. Chiasson wrote:
> Hi, I recently upgraded our servers to mod_perl 1.24.1 so I decided to
> give DSO mod_perl a try.  And it now works perfectly, even with our perl
> modules implementing core httpd configuration directives (Wich was broken
> under DSO until 24.1)
> 
> So, I decided to start playing with restart/graceful too, thinking that DSO might 
>solve
> the problems of cleanly restarting a mod_perl server without loss of service...
> 
> Here is a bit of top while restarting my server a few times.... :

[....]

I've found that mod_so combined with Perl's dynamic loading causes this memory 
leakage.  

I ended up compiling apache without mod_so (i.e. all modules compiled in static, no 
DSO) and
I do not see this memory leakage at all.

> And everything apparently behaves fine and keeps on working, but my main question is 
>where is the 12Mb that adds to
> each process on restart comes from ? What is hapenning ?
> 
> I know these issues have been brought before in the case of statically compiled-in 
>mod_perl, but doesn't restarting the
> server freeing libperl.so and re-loading it freshly ?
> 
> Any information would be more than welcome ...
> 
> ## My version info is :
> Redhat 6.2 running on a i386 Linux 2.2.17
> 
> Server version: Apache/1.3.14 (Unix)
> Server built:   Oct 18 2000 14:00:36
> 
> perl5 (5.0 patchlevel 5 subversion 3)
> 
> mod_perl 1.24.1
> 
> /usr/local/apache/bin/httpd  -l
> Compiled-in modules:
>   http_core.c
>   mod_so.c
> 
> 
> -- 
> +-----------------------------------------------+
> | Philippe M. Chiasson  <[EMAIL PROTECTED]> |
> | SmartWorker http://www.smartworker.org        |
> |     IM : gozerhbe  ICQ : gozer/18279998       |
> +-----------------------------------------------+
> /*   * Hash table gook..   */ 
>       -- Linux        2.4.0-test2
>       /usr/src/linux/fs/buffer.c
> 
> perl -e '$$=\${gozer};{$_=unpack(P26,pack(L,$$));/^Just Another Perl 
>Hacker!\n$/&&print||$$++&&redo}'



-- 
Paul Lindner
[EMAIL PROTECTED]
Red Hat Inc.

Reply via email to