digg

Join DiggAbout

Discover the best of the web!
Learn more about Digg by taking the tour.

See the original image at dromaeo.com

Dromaeo: Mozilla's JavaScript Performance Testing

dromaeo.com — Test your JavaScript performance in many various browsers such as Firefox 2+, Safari 3+, and Opera 9+, and Internet Explorer 6+

Bury
show profanity settings
expand all
  • rdrysdale, on 04/11/2008, -2/+4In case anyone missed it, the header moves, too. heh, fun dinos.
  • davidblog.com, on 04/11/2008, -1/+3Very nice utility, but it's the dinosaurs that make it rad!
  • trib4lmaniac, on 04/11/2008, -1/+10FYI: Dromaeo was developed by the John Resig, author of the jQuery JavaScript library.

    http://ejohn.org/blog/dromaeo-javascript-performan ...
  • Mislav, on 04/11/2008, -1/+2Read more in the Mozilla wiki: http://wiki.mozilla.org/Dromaeo
    It documents much more stuff that aren't immediately obvious.
  • dubness, on 04/11/2008, -1/+3Will John Resig never stop? That guy is a machine!
  • Lazdude, on 04/11/2008, -5/+0I'm guessing Opera will outperform the rest, and Firefox will come out second best.
  • floor, on 04/11/2008, -2/+1On my dual G5 Mac, Safari was 3x faster than Firefox.
    • sq377, on 04/11/2008, -0/+1On my linux system, epiphany with webkit ran a lot faster than firefox-3.0-b5 as well.
    • iainc, on 04/11/2008, -0/+1Hmmm, FFX3b5 beats Safari 3.1 by approx 150 ms in completing the entire battery of tests on my MacBook Pro 2.3GHz.
  • feedmeplz, on 04/11/2008, -4/+1So why did Mozilla go and build a completely separate JavaScript benchmark when the existing SunSpider benchmark, developed by the WebKit team, exists and is open source? The comments on John Resig's blog post indicate problems with the methodology of the new Mozilla benchmark (http://ejohn.org/blog/dromaeo-javascript-performan ... which weakens their claims of creating a "statistically sound" benchmark. The open and collaborative approach here would have been for Mozilla to collaborate with WebKit on their *existing* benchmark suite, rather than creating their own (even re-using many of the same tests) and then claiming to want to collaborate with other browser vendors. There's an awful lot of talk about "openness" and "collaboration" from Mozilla, but this goes to show that talk is all it is.
    • comrade693, on 04/12/2008, -1/+2I see *one* comment that says that, and John replied to it here: http://ejohn.org/blog/dromaeo-javascript-performan ...

      Excerpt:
      @Gavin Brown: You didn't actually read the blog post or wiki page, did you? How about you take a gander through the methodology to get a feel for why SunSpider was inadequate. It's important to note the difference between a testing suite and a suite of tests, as well. Dromaeo will eventually include all of the tests that are in SunSpider, plus many more. The tests that SunSpider provided were adequate, for now (which is why we're standardizing on them) the suite, was not.
      And as I mentioned in the post, we're working with the WebKit team - along with the other browser vendors - to standardize on a suite of tests.
      • bdash, on 04/12/2008, -0/+1Did you happen to miss the two comments from Maciej Stachowiak?

        """
        I think Dromaeo's testing methodology has significant flaws in itself. First of all, it wraps every test in a closure, which factors out the performance of access to globals (something that actually matters for real scripts). Second, the way it determines two results are a "tie" is statistically unsound - you can't just check if two confidence intervals overlap, you have to do a two-variable t-test, which SunSpider does correctly. Third, running a test more times if the variance is higher than some threshold creates statistical artifacts - it's not good science to change an experiment midstream based on statistical results, and it makes it impossible to do statistical analysis on the totals since you can't meaningfully generate 5 totals if some tests ran more than 5 times. Fourth, Dromaeo seems to report much higher variance than SunSpider, so it is likely that the harness is interfering with the execution of the tests more than on SunSpider and creating noise.
        """
  •  

    Login or register to add a comment

    Create a new account or login to join in the conversation on Digg. You'll also be able to Digg stories to help promote things you like.


© Digg Inc. 2008 — Content posted by Digg users is dedicated to the public domain.
DIGG, DIGG IT, DUGG, DIGG THIS, Digg graphics, logos, designs, page headers, button icons, scripts, and other service names are the trademarks of Digg Inc.