Benchmark Battle, September 2015: Chrome Vs. Firefox Vs. Edge
An anonymous reader writes: The next browser battle is upon us. Edge has been out for more than a month, and its two biggest competitors have received significant updates: Chrome 45 and Firefox 40. This article puts all three through their paces, and each manages to win a few tests. Edge convincingly won the JetSteam and SunSpider JavaScript benchmarks, while also eking out a victory in Google's Octane test. Chrome was victorious in Mozilla's Kraken benchmark for JavaScript performance, while also edging out Firefox in HTML5Test and the Oort Online WebGL test. Firefox won the WebXPRT test that combines HTML5 and JavaScript performance, and also the Peacekeeper test for general browser performance. There's no clear dominant browser for performance, and none of the three are obvious laggards, either. Browser competition seems to be in a good place right now.
With FF and Chrome JavaScript performance has been good enough for most web apps for the past couple of years. Good to see IE has caught up, but JS performance is not been what's hold the web back. The issue is DOM performance. For example, my stock trading app eats up 100% of my CPU time and causes Firefox UI to get unresponsive when tracking more than 30 stocks. Their native IOS app barely uses any CPU time and runs better on my phone than the web app on my desktop. It's time we ditch DOM's document based model for something application centrist.
Why on earth would I care at all about "performance" in my web browser. Unless its 10x slower, seriously who cares?
What I care about are:
Obviously you can't get perfect in either, but I'll err on the side of coming closest to these marks.
Why? Do you think Microsoft's OS has some magic CPU cycles set apart for their browser?