Google Git
Sign in
chromium / external / github.com / WebKit / Speedometer / f227c26c11e83f07c90c28c89a824f81db9d05c6
commitf227c26c11e83f07c90c28c89a824f81db9d05c6[log] [tgz]
authorCamillo Bruni <[email protected]>Tue Mar 04 15:42:01 2025
committerCamillo Bruni <[email protected]>Tue Mar 04 16:07:58 2025
treee42da8e29119b64fe35dc20728a9eb68a64975bc
parenta4d98e20f93f1a79ab738cbd6a5c21b2e731a115 [diff]
Add params.leakyIframes to main-custom

DevTools can't handle sources from detached iframes.
To simplify local development we add an an option that just hides
the iframes away but never detaches them from the DOM.

Change-Id: I4aeb079a8757de140f7ca0affe5ece931dadfc7a
5 files changed
tree: e42da8e29119b64fe35dc20728a9eb68a64975bc
  1. .github/
  2. experimental/
  3. resources/
  4. tests/
  5. .eslintignore
  6. .eslintrc
  7. .gitignore
  8. .npmrc
  9. .prettierignore
  10. .prettierrc
  11. about.html
  12. babel.config.json
  13. Development.md
  14. Governance.md
  15. index.html
  16. instructions.html
  17. LICENSE
  18. netlify.toml
  19. package-lock.json
  20. package.json
  21. README.md
  22. Testing.md
README.md

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.

Score and Test Measurement

Each test can contain several steps who contributed to the test duration. Note that the prepare step of a test is unmeasured and thus does not contribute to the score. All following test steps are measured and summed up in the test step time.

Each step consists of the following phases:

Score

The final benchmark score is calculated based of the inverse of geomean of all tests. We average the score over multiple iterations with the arithmetic mean. By using the geomean to combine the test durations we maintain the invariant that relative improvements are favoured equally amongst all tests, even though they can have vastly different durations.