The idea of a memory limit is to as accurately as possible account
for the memory utilized by PHP. If our current calculation is more
accurate since it accounts for malloc overhead, great, it gives more
fine grained control to hosters utilizing this option.
On 25-Jul-06, at 9:45 AM, Lukas Smith wrote:
Dmitry Stogov wrote:
Right now memory_get[peak_]usage() show the amount of REAL memory
that PHP
(Zend Memory Manager) takes from system.
Previous memory manager showed size of emalloc()-ed memory without
malloc()
overhead.
Also it didn't consider internal caches.
Shouldn't we make the old behavior the default here?
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Ilia Alshanetsky
