Browser Benchmark Analysis and Data
Most browser benchmarks are isolated, artificial tests that can be gamed by browser vendors optimizing those specific cases. With only those benchmarks to go on, we were skeptical that IE9′s beta would actually outperform other modern browsers in real-world applications.
To separate hype from reality, we built our first browser benchmarking tool based in LucidChart itself. The benchmark works by simply dragging a part of the diagram around the page for five seconds. We measured the total frames per second over that period, plus how the frame rendering time was split between actual javascript execution and the “inter-frame” period.
Javascript engines have become so fast that the majority of time is now spent in between render calls for all the browsers we tested. This is the time the browser spends actually drawing the page we set up during our render code, along with whatever other miscellaneous things may delay the next frame from starting.
The Big Picture
Chrome is the obvious winner in this benchmark. While Opera, Safari, and the IE9 beta approach Chrome in raw Javascript speed, those browsers drop far behind by taking too long to actually draw the image set up by the Javascript and get back into rendering the next frame.
Surprisingly, Firefox 4.0 Beta 6 came in behind all other browsers except for IE8–even coming in behind its predecessor, Firefox 3.6. While we expect its performance to improve before release, it was surprising to see this result. It should be noted that no Firefox 4.0 Beta 6 test run came in faster than any test run by another modern browser.
IE9 Beta 1 performed surprisingly well (with a few caveats; see the notes below). In fact, it performs well enough that LucidChart will finally be able to remove the obnoxious warning to IE users that they’re getting an inferior experience in LucidChart.
Testing Methods
These tests were conducted on a Windows 7 x64 laptop running a Core i7 Q720 CPU with 4GB of DDR3 RAM.
For each browser tested, we closed and relaunched the browser before each trial, and the window size was consistent across all trials. The document for the benchmark was very similar to our standard business process template, of moderate complexity. We ran four trials for each browser, and the results shown here are averaged across those trials.
Some final notes on Firefox 4 Beta 6
In several trials on Firefox 4 Beta 6, performance absolutely tanked due to the browser doing some unknown background work. These trials were discarded for the purpose of this data, but it should be noted that Firefox 4 may have inconsistent performance for certain types of modern web applications, like LucidChart.
Some final notes on IE9 Beta 1
When we first attempted the benchmark in IE9 beta 1, we got results only about twice as fast as in IE8, and many times slower than all the other browsers tested. This actually led us to fix a minor flaw in our rendering algorithm that had us performing many more DOM operations that we needed to during rendering. Removing that flaw let IE9 catch up to most of the other browsers (Chrome excluded).
So while Javascript and rendering performance in IE9 are respectable, DOM manipulation seems to be nearly as slow as ever. This benchmark should be taken for what it is–one representative example of one modern web application’s performance in these browsers. IE9 performance does drop precipitously under certain workloads.
Run the benchmark yourself
This benchmark can be run by anyone in LucidChart. First, sign up for a free account. Then create a document that you’d like to benchmark. Right-click the block you’d like to have dragged around the page by the benchmark, and click “Bring to Front.” The benchmark uses the topmost block for its test. Then click the tools menu, and select “Benchmark Performance.”
About the author
Dav Gra is interested in the latest trends of online collaborative solutions for distributed teams, including an online tool where users can create a network diagram or UML diagram.