Oh god, just when web people were starting to understand how to create good benchmarks (<a href="https://blog.mozilla.org/nnethercote/2012/08/24/octane-minus-v8/" rel="nofollow">https://blog.mozilla.org/nnethercote/2012/08/24/octane-minus...</a>), now we're going back to 1980s microbenchmark hell.<p>Doesn't anyone read Hennessy and Patterson any more? The best benchmarks are real apps, not crappy little microbenchmarks that measure a single thing.<p>(Can you hear that thud, thud, thud? It's the sound of me beating my head against my desk.)
Doesn't run that well on my android phone, since my browser has only 2 modes of pop-up handling: deny all and confirm each.<p>In firefox-ESR on Win7-64 it seems to get stuck in one of the SVG tests, unless it's supposed to take an extraordinarily long time (I killed it after 15+ minutes).<p>Neat idea, though. I love having a great go-to benchmark for web, so I have a good baseline for expectations when whipping up mobile sites.
How do browser benchmarks account for incorrectly drawn or spaced items. Could I write a browser that will ignore everything except the elapsed time measure?
Nice to see getters/setters in there. Performance for them is absolutely abysmal in modern runtimes. :(<p>EDIT: Is it my imagination or is it really difficult to find a link to RobotHornet itself in the OP?