4332004a86
For locall investigation we found that having these additional delay params was very helpful: - waitAfterSetup: Post setup delay (before running the steps) - waitAfterSuite: Post suite delay (after running all steps) |
||
|---|---|---|
| .github/workflows | ||
| resources | ||
| suites | ||
| suites-experimental | ||
| tests | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .npmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| about.html | ||
| babel.config.json | ||
| Development.md | ||
| Governance.md | ||
| index.html | ||
| instructions.html | ||
| LICENSE | ||
| netlify.toml | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| Testing.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:
- Sync:
- Time spent in synchronous JS execution.
- Async:
- Time spent in asynchronous JS like Promise or setTimeout tasks scheduled by the sync-step.
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.
