Re: cvs: php-benchmarks /benchcli/tests test_whirl.php /benchcli/tests/phpWhirl 99bottles.wr AUTHORS COPYING keymaker.wr whirl.php
/benchcli/tests/phpWhirl/classes WhirlMathRing.php WhirlMemory.php WhirlOpsRing.php WhirlParser.php WhirlRing.

On Tue, Jun 2, 2009 at 9:13 PM, Nuno Lopes <nlopess@php.net> wrote: >> For memory allocation: > > Let me just add a few more options: > - valgrind has a tool named helgrind, which is a heap profiler (I presume you mean massif?) Hmmm. I had suggested that Alexander use the "memory allocated" statistic of valgrind as a surrogate for the data provided by massif. Massif reports the memory used at certain intervals, which is probably the ideal result: the sum of the memory reported every 1/X seconds. The problem was the valgrind is too slow, and massif is probably slower (but I am not sure). I think using a profiling malloc library would be faster, but I'm not sure what the options are here. > - Zend's memory allocator provides some statistics, including the user-land > function: http://php.net/memory_get_usage For the reasons above, I don't think this (or memory_get_peak_usage) is suitable. Thanks, Paul -- Paul Biggar paul.biggar@gmail.com