LearnActual JavaScript Engine Performance

writes on May 2, 2011

This page on Actual JavaScript Engine Performance by Douglas Crockford is really interesting. For bonus points, read the JSMeter paper Douglas links to. It’s absolutely true that we should be testing real application performance rather than benchmarking made up scenarios, and it’s good to see some performance data from JSLint.

I think I’m mainly impressed to see that all of the JavaScript engines are ridiculously fast these days. Hats off to the IE team for being the best browser on that list. I certainly wouldn’t have expected to see that a couple of years ago.

5 Responses to “Actual JavaScript Engine Performance”

  1. go onto the adobe flash player website and u can download it for free hope this helps good luck 🙂


  2. I am considering to move from my current Applications Support role to Java Development but I am not sure if I do the right thing because there are a lot of developers already with more experience plus some companies are outsourcing the programming work to India, etc.


  3. Replica watches on May 4, 2011 at 2:03 am said:

    They not only work fine and affordable …..
    IWC Watches
    Men Longines Watches

  4. Tudmotu on May 3, 2011 at 12:46 pm said:

    The claim that “all of the JavaScript engines are ridiculously fast these days”, is, for itself, ridiculous.
    This is just not true. Try running complex calculations written in JS from within a browser, and then try to run the same calculations outside the browser with a stand alone interpreter – you will see a difference. More over, try running the same calculations in another high-level programming language, such as Perl, Ruby, or Python, and you will see that in fact, modern browsers are very slow in comparison to stand alone interpreters of other languages.
    This does not mean that JS for itself is slow, but the implementation of ECMA interpreters is weak in performance.


  5. It’s interesting to see IE’s JS speeds have improved, but I think it’s like comparing frames per second in Doom to Crysis. If you leave out 50% of the DOM, CSS3, HTML5 abilities, and commit your resources to JS, your bound to get impressive numbers on strict JS.

Leave a Reply

You must be logged in to post a comment.

Want to learn more about Javascript?

Learn how to use JavaScript to add interactivity to websites.

Learn more