Hi,
I invested about half an hour this morning to refactor bench.php. It now
starts a new PHP process for each benchmark and uses microtime(true) and
memory_get_peak_usage() to measure benchmark data.
Have a look at
- http://phpfi.com/208939
This is the main script.
-
On 02/27/2007 01:23 PM, Sebastian Bergmann wrote:
Here is an example output:
[EMAIL PROTECTED] benchmark % php run.php
Benchmark Time Peak Memory Usage
ackermann 3.067452 715080
mandel 2.242472 127840
mandel2 2.185040 123448
Antony Dovgal wrote:
I like it. Please continue.
Okay, great. Now: where should I put it? I think the current approach of
having bench.php duplicated in each branch of the Zend Engine is sub-
optimal. Maybe we could create a new top-level CVS module for this?
--
Sebastian Bergmann
Sebastian Bergmann wrote:
Have a look at
I uploaded a snapshot of what I have now (I added fallbacks for missing
functionality in PHP 4.4 and PHP 5.0 and the rest of the benchmarks) to
http://static.phpunit.de/benchmark.tbz2.
--
Sebastian Bergmann
On 02/27/2007 02:42 PM, Sebastian Bergmann wrote:
Antony Dovgal wrote:
I like it. Please continue.
Okay, great. Now: where should I put it? I think the current approach of
having bench.php duplicated in each branch of the Zend Engine is sub-
optimal. Maybe we could create a new top-level
From: Arnold Daniels [mailto:[EMAIL PROTECTED]
DirectoryIteratorRecursive:
- Add flag DIRS_ONLY for the constructor, to only loop through
directories
This is achieved by a FilterIterator: ParentIterator
Yes but if you want to loop recursively through the directories,
Hello Antony,
QA sounds fine. Top-level is also fine as we have no real mathing place.
When we offer it through QA we might aswell use qw-web as the cvs module
but a seperate one sounds better.
best regards
marcus
Tuesday, February 27, 2007, 5:58:41 PM, you wrote:
On 02/27/2007 02:42 PM,
Hello Sebastian,
looks pretty fine. Only you don't need fallbacks right now. Simply add a
check for PHP = 5.2.0 since you are using Iterators and I don't see any
sense in testing 5.0 or 5.1. You could further more make the run script
operate a bit like run-tests.php and have the PHP executable
On 02/27/2007 11:48 PM, Marcus Boerger wrote:
Hello Antony,
QA sounds fine. Top-level is also fine as we have no real mathing place.
I meant using qa.php.net for releases, I don't care where exactly it lives in
our CVS.
When we offer it through QA we might aswell use qw-web as the cvs
Hi all.
[Please, let me know if there is a better place to ask such questions.]
In a Zend extension I'm working on, I need to perform some actions
when certain instructions (zend_ops) are executed by the VM. Note that
I'm interesting in specific instructions rather than instruction
types, e.g.,
Andrew Hutchings writes
I dunno what the heck I am doing wrong then :)
I have tried on a PPC running OSX, a Xen host on a Dual Xeon
running Ubuntu Edgy, an EPIA running Ubuntu Edgy and the Xeon
devel box.
When configuring with ./configure --disable-all
--disable-cgi and compiling with
I've run the bench on a development box at work. A hefty box with no load,
running Fedora Core 5.
The strcat results were approximately *10 times slower* on 5.2.1 than on
5.2.0.
Everything else was nominal.
Could you send your phpinfo() and the script you tested (or if it was
bench.php from
Stanislav Malyshev schrieb:
The strcat results were approximately *10 times slower* on 5.2.1 than on
5.2.0.
Everything else was nominal.
Could you send your phpinfo() and the script you tested (or if it was
bench.php from CVS then its output)?
I see only tests on *nix boxes... Here is
The strcat results were approximately *10 times slower* on 5.2.1 than on
5.2.0.
Upping the number significantly (from 20 to 2000) smooths out
abnormalities:
5.2.0:
strcat(2000) 5.556
5.2.1:
strcat(2000) 5.628
These results are typical for a few runs of each (fresh
Marcus Boerger wrote:
Only you don't need fallbacks right now. Simply add a check for
PHP = 5.2.0 since you are using Iterators and I don't see any sense
in testing 5.0 or 5.1.
Already did that yesterday.
You could further more make the run script operate a bit like
run-tests.php and have
Sebastian Bergmann wrote:
I uploaded a snapshot of what I have now (I added fallbacks for missing
functionality in PHP 4.4 and PHP 5.0 and the rest of the benchmarks) to
http://static.phpunit.de/benchmark.tbz2.
I updated the snapshot. This is what the output looks like now:
Benchmark
16 matches
Mail list logo
