Many enthusiasts want a fast browser, and they want to consistently and easily measure the performance of different browsers. There are lots of “benchmarks”
in the history of software, and lots of benchmarks around browsers. The challenge with benchmarks is generally understanding what the benchmark measures and deciding whether those measurements are important to customers, developers, and you.
This blog post takes a closer look at some of today’s most common benchmarks. We’ll provide context on their origins, talk about what they test, and show you what browser subsystems
each benchmark executes. Celtic KaneCeltic Kane
was designed to help Google tune
The Flying Images
demo released with the first Internet Explorer Platform Preview
The FishIE Tank
demo released with the third Internet Explorer Platform Preview
The Psychedelic Browsing
demo has received over 500,000 page views over the last five weeks since the fourth Internet Explorer Platform Preview
We believe that to build a fast real world browser you have to start by understanding the real world patterns
and design the right systems around those patterns. You can’t build a fast real world browser by optimizing for benchmarks. And you can’t accurately assess a browsers performance by looking solely at the results from benchmarks. When used for engineering purposes, benchmarks can be an effective tool to help understand the implications of code changes. That’s where the value ends though.
As an industry we have to care be careful that we don’t lose sight of what’s important – the real world customer scenarios of today and the HTML5 scenarios of tomorrow.
Lead Program Manager, Internet Explorer Performance