Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42553
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender)
Message-ID: <4969B6C9.4070903@daylessday.org>
Date: Sun, 11 Jan 2009 12:07:21 +0300
User-Agent: Thunderbird 2.0.0.19 (X11/20081227)
MIME-Version: 1.0
To: jvlad <dmda@yandex.ru>
CC: internals@lists.php.net
References: <200901101830.35403.thomas@koch.ro> <8E.40.26912.68B39694@pb1.pair.com>
In-Reply-To: <8E.40.26912.68B39694@pb1.pair.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: php daemons, memory
From: tony@daylessday.org (Antony Dovgal)

On 11.01.2009 03:21, jvlad wrote:
> Almost.
> Try to compile your very-own-version of php, using configure argument
> --disable-zend-memory-manager

There is no such configure option since ages.
Zend MM can be disabled by setting USE_ZEND_ALLOC env var to 0, but only when 
--enable-debug is used (since nobody is supposed to do that except for debugging 
purposes).

> also, disable _all_ php extensions that your scripts do not depend on.

That won't affect memory usage very much.

> - --enable-debug did report some small leaks, but much less then the
>>  consumption grow.
> 
> zend memory manager won't release memory to the system. 

That's plain wrong.
Of course it does free() memory whenever it thinks the memory should be free()-ed. 
Though that doesn't guarantee that the OS is be able to reuse this memory.

-- 
Wbr, 
Antony Dovgal