Manual-sync mirror of chromium.googlesource.com/external/github.com/WebKit/Speedometer.git
Find a file
Camillo Bruni 76f4bb1e86
Use Score instead of Runs / Minute (#61)
RPM has always been a bit a confusing term in Speedometer2 as it was never real rpms, rather a scaled value.
To avoid future confusion it is renamed to the more neutral term "Score".
2023-02-09 09:42:13 +01:00
.github/workflows Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
resources Use Score instead of Runs / Minute (#61) 2023-02-09 09:42:13 +01:00
tests Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
.eslintignore Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
.eslintrc Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
.gitignore Adds unit tests for BenchmarkRunner using Mocha (#40) 2023-01-26 09:06:59 -08:00
.npmrc Dev setup (#55) 2023-01-30 14:52:46 -08:00
.prettierignore Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
.prettierrc Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
Development.md Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
Governance.md Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
index.html Use Score instead of Runs / Minute (#61) 2023-02-09 09:42:13 +01:00
InteractiveRunner.html Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
LICENSE Reviewed by Addy Osmani and Jonathan Bedard. (#2) 2022-06-29 11:40:19 -07:00
package-lock.json Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
package.json Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
README.md Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00
Testing.md Add Eslint & Prettier (#57) 2023-02-08 13:53:53 -08:00

⚠️ Speedometer 3 is in active development and is unstable. You can follow along with development in this repository, but see Speedometer 2.1 for the latest stable version.

What is Speedometer?

Speedometer is a benchmark for web browsers that measures Web application responsiveness by timing simulated user interactions on various workloads. Our primary goal is to make it reflect the real-world Web as much as possible. When a browser improves its score on the benchmark, actual users should benefit. In order to achieve this, it should:

  • Test end-to-end user journeys instead of testing specific features in a tight loop. Each test should exercise the full set of what’s needed from the engine in order for a user to accomplish a task.
  • Evolve over time, adapting to the present Web on a regular basis. This should be informed by current usage data, and by consensus about features which are important for engines to optimize to provide a consistent experience for users and site authors.
  • Be accessible to the public and useful to browser engineers. It should run in every modern browser by visiting a normal web page. It should run relatively quickly, while providing enough test coverage to be reflective of the real-world Web.