>> seems you're flying too high.
>> RHEL5 still ships php5.1.6 and it has this option and it undefines
>> ZEND_USE_ZEND_ALLOC.
>
> PHP 5.2.0 has been released more than 2 (two) years ago, which should be
> enough for a distro to catch up, don't you think so?
Perhaps. But what they ship with RHEL5
On 11.01.2009 17:51, jvlad wrote:
>> 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.
>
> seems you're flying too high.
> RHEL5 still ships p
> ZMM does never release memory to the system.
my appologies, "never" is a too strong word for that. I'd use "almost
never".
Indeed ZMM does release segment to the OS if all the memory blocks in it are
freed.
I'd only add that with an average script, it won't happen.
jv
--
PHP Internals - P
> 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.
seems you're flying too high.
RHEL5 still ships php5.1.6 and it has this option and it undefine
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 (s
> Since I use a MySQL connection, Syslog and many classes, I wanted to let
> the script run a while before restarting. So the scripts had lines like:
>
> $i = 1000;
> while( --$i )
> {
> while( run() ); // run returns false if there are no pending jobs
> gc_collect_cycles();
> // echo get_memory
