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 4:26 PM, Paul Biggar <paul.biggar@gmail.com> wrote: > On Tue, Jun 2, 2009 at 3:09 PM, Alexander Hjalmarsson <hjalle@sgh.se> > wrote: > > On Tue, Jun 2, 2009 at 3:43 PM, Paul Biggar <paul.biggar@gmail.com> > wrote: > >> > >> On Tue, Jun 2, 2009 at 2:32 PM, Alexander Hjalmarsson <hjalle@sgh.se> > >> wrote: > >> > This benchmark, when running parsing keymaker.wr, takes pretty long > time > >> > for > >> > me (about 1 minute on a slow machine). If I run 99bottles instead, > which > >> > is > >> > a smaller program, it takes about 10 seconds instead. Is 1 minute > >> > acceptable > >> > or should we go for the other, 99bottles? > >> > >> I've found in my benchmarking that its useful to have a set of > >> benchmarks which run very quickly, and another set where I can be > >> surer of the results. How long do the other benchmarks run for? > > > > > > The tests are running at about 3-10 seconds. Maybe it's a good idea to > have > > an argument for a longer run (like running the keymaker instead of > > 99bottles), but in that case, the micro benchmarks would be pretty > useless > > as they would only increase the iteration-times. > > I wouldn't worry too much about the micro-benchmarks. They wouldnt be > much worse than they are now. That might be correct. :) When adding up the cachegrind time (or valgrind), the time for the benchmark would be as you know, about 20x longe. How long is reasonable for a benchmark to run? I'm mostly thinking of when enabling valgrind/cachegrind or any other tool. > > The other test I just > > uploaded also have a similar problem, though its the opposite. I just > have > > working input thats like 1000 characters long, which makes the benchmark > to > > only take like 3/4 of a second. It would be good to have better input > data > > for that test, but it didn't work with more advanced javascripts such as > the > > V8-benchmarks and similar. Do anyone know any "simple" input that might > > work, but that yet is pretty comprehensive? > > I think you forgot to say which test need the input? > Boh. I'm talking about the test for the j4p5 parser, found here: http://j4p5.sourceforge.net/index.php The indata that is used now is the example1, found here: http://j4p5.sourceforge.net/demos/2.php It's not really anything to work with and I think it would be good to have something larger. > > > Paul > > > > > >> > On Tue, Jun 2, 2009 at 3:19 PM, Alexander Hjalmarsson > >> > <hjalle@php.net>wrote: > >> > > >> >> hjalle Tue Jun 2 13:19:40 2009 UTC > >> >> > >> >> Added files: > >> >> /php-benchmarks/benchcli/tests test_whirl.php > >> >> /php-benchmarks/benchcli/tests/phpWhirl 99bottles.wr AUTHORS > >> >> COPYING keymaker.wr > >> >> whirl.php > >> >> /php-benchmarks/benchcli/tests/phpWhirl/classes > >> >> WhirlMathRing.php > >> >> > WhirlMemory.php > >> >> > WhirlOpsRing.php > >> >> > WhirlParser.php > >> >> WhirlRing.php > >> >> Log: > >> >> Whirl parser test > >> >> > >> >> > >> >> -- > >> >> PHP Quality Assurance Mailing List > >> >> <http://www.php.net/> > >> >> To unsubscribe, visit: > >> >> http://www.php.net/unsub.php > >> >> > >> > > >> > >> > >> > >> -- > >> Paul Biggar > >> paul.biggar@gmail.com > > > > > > > > -- > Paul Biggar > paul.biggar@gmail.com >