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

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/