Re: Fw: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

shared libraries save memory (and disk space) if and only if they are used by different programs simultaneously in the case of apache there is usually no such gain as apache is started only once and then creates its process farm using fork(), so that all theese processes share their code and static data anyway compiling everything in statically gives a performance gain (depending on the cpu architecture, on ia32 it can be significant, on cpus like e.g. sparc this will be less obvious due to their bigger register sets) and might ease debugging when you are in trouble, but this is not an agrument for production environments Jason Greene wrote: > > Becuase DSO's are shared libs. Here is an excerpt about shared libs: > > The shared library code is not present in the executable image on disk. > Shared code is loaded into memory once in the shared library segment and shared by all > processes that reference it. > [...] > > Zeev Suraski wrote: > > > > Why would using DSO reduce memory consumption? > > Using DSO makes things easier to administer and maintain, but it doesn't > > save any memory and it does pose a slight performance decrease... > > > > At 02:20 30/1/2001, Jason Greene wrote: > > >MaxRequestsPerChild is perfectly safe, and I always believe in setting it. > > >Keep in mind that if you compile all modules into apache statically, it takes > > >up far more base mem per process. If you use all DSO's, you can > > >significantly reduce memory usage. To find out what's in use on RH7 > > >cat /proc/<pid>/maps of an apache child. > > >You can also reduce the KeepAlive timeout value to help-out. -- Hartmut Holzgraefe hartmut@six.de http://www.six.de +49-711-99091-77 Besuchen Sie uns auf der CeBIT 2001 - in Halle 6 Stand F62/4