Although speed is a major factor in browser choice, many people don't want to know why their favorite browser is fast -- they just care that it is. But the standards and tests used to determine how we measure a browser's speed can be varied, so Google has set out to further define the playing field.
This doesn't appear to be a case of the tech giant stomping all over open standards, though. Octane v1 is a revamp of Google's V8 benchmark and adds five tests to the eight current ones, the company said today in a blog post announcing Octane.
Octane is the evolution of V8, said Cazzulani. "V8 will still be there, still interesting, but the new [tests] are where we are focusing for today's users. We'd like everybody [who benchmarks browsers] to use that."
As with the V8 benchmark, the higher the score, the better the result. My informal testing put Chrome 21 at an Octane version 1 score of 4,945 and a V8 version 7 score of 4,221. Firefox 14 hit 3,090 on Octane, and 2,404 on V8.
Cazzulani also noted that older mobile devices will struggle with the test, although in casual tests I noticed that to be true with more than just mobile devices. Both Firefox 15 beta for Android and Opera 12 for Android struggled to finish the test, while Chrome for Android cruised through it. There are several reasons why this could be, including that the version of the test I was running still had unfixed bugs, or that there are still problems with the test implementation itself. Since the test is new, it's hard to say.
Cazzulani was honest about the limitations of the test, too. He said that Octane itself has revealed areas for improvement for the V8 team, although he refused to say more about such areas. "We've seen that the other guys are doing a great job. Of course, we optimize for the V8 every day, but we need something to guide us in the future. We have work to do."
Updated 12:25 p.m. PT: Google has released a chart showing browser compatibility with Octane. For desktops, Safari v5.1.7 is on the list, but Internet Explorer 9 is not. On mobile, both Chrome and Safari on iOS fail because they share the restrictions associated with the older version of WebKit.