Bug 177559 - Speedometer 2.0: Browser-vendor sign-off
Summary: Speedometer 2.0: Browser-vendor sign-off
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
Depends on:
Blocks: 172339
  Show dependency treegraph
Reported: 2017-09-27 11:59 PDT by Addy Osmani
Modified: 2017-12-20 11:03 PST (History)
6 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Addy Osmani 2017-09-27 11:59:07 PDT
As we near finalization of Speedometer 2.0, we would like other browser vendors to give us their sign-off on this iteration so that we can ship the benchmark. This is not a blocker for launching, but we would like to try seeking an "LGTM" or call-out of any major changes considered outstanding.

The latest version of the benchmark is hosted up on:

(Thanks to Ryosuke for deploying it)

We have heard feedback at numerous points during development from the likes of Mozilla and Intel. It would be valuable to get a confirm from folks that they feel the benchmark is in a sufficiently solid state from their perspective.

Any issues currently labelled as blockers (at this time, an about page and discussion on inferno) will of course be discussed to resolution before shipping.
Comment 1 Harald Kirschner 2017-09-27 16:34:19 PDT
A big thanks to everybody involved for the substantial work on Speedometer 2.0 and the prior 1.0. It's vital to the web that engine developers compete on benchmarks that matter; not for he sake of numbers but to make the web better for users and make life easier for web developers.

We have been optimizing against Speedometer 2.0 for a few months now, following the development closely. We've been happy with the decisions that went into 2.0, like the choices of frameworks and geometric mean and consider the benchmark to be in a solid state.

Comment 2 Daniel Clifford 2017-09-28 10:21:33 PDT
We've been internally testing Speedometer 2.0 to track V8's performance for the last few months. After providing feedback that has already been addressed we are happy to support the benchmark shipping in the current state.

Thanks to everybody who contributed to making Speedometer 2.0 a reality. It's exciting to see such a large cooperative investment into a benchmark that tries to reflect workloads that matter to developers and users.

Comment 3 Ryosuke Niwa 2017-12-20 11:03:24 PST
I think we're good here.