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

As Hartmut said, this argument is invalid in the Apache environment. All the static code in Apache is loaded to memory only once (in copy-on-write pages, that will never be written to). Using DSO's in Apache has no advantages other than ease of administration (which is an important thing by itself for many), and some disadvantages. Zeev At 08:17 6/2/2001, 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. The advantages of shared libraries are:

      Less disk space is used because the shared library code is not included in the executable programs.
      Less memory is used because the shared library code is only loaded once.
      Load time may be reduced because the shared library code may already be in memory.
      Performance may be improved because fewer page faults will be generated when the shared library code is already in memory.

However, there is a

      performance cost in calls to shared library routines of one to eight instructions.

Jason 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... Zeev 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. Jason

----- Original Message ----- From: "Rasmus Lerdorf" <rasmus@linuxcare.com> To: "Filip Sielimowicz" <sielim@wp-sa.pl> Cc: <php-dev@lists.php.net> Sent: Monday, January 29, 2001 7:51 AM Subject: Re: [PHP-DEV] PHP 4.0 Bug #8889: Memory is not being freed.

On Mon, 29 Jan 2001, Filip Sielimowicz wrote:

A quick fix would be to set your MaxRequestsPerChild to a lower

value.

Have you ever tried to measure the time of killing and starting httpd process ? You can see that with a bare human eye.

Sure. But that isn't something that happens on an actual

request, so an

end user isn't going to see that. -Rasmus -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail:

php-list-admin@lists.php.net

-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net

-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net

-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/