| commit | 3d6d8c8015b5f36b1775b4c5920d173ed6b2cf75 | [log] [tgz] |
|---|---|---|
| author | Camillo Bruni <cbruni@chromium.org> | Wed Sep 21 09:39:26 2022 |
| committer | Camillo Bruni <cbruni@chromium.org> | Wed Sep 21 09:39:26 2022 |
| tree | ad4827500c1d28fc2bd962f617dab7e72a46082c | |
| parent | 79e599c5a00228b4209894b7878add62d7053545 [diff] |
Split Benchmark and Runner into separate classes - Move Benchmark into benchmarks/base.py - Reducing dependencies of benchmarks.* modules and only include the full module while typing Change-Id: Ibd1bb1a187078fa6f76fdf637ef18fcb22eb9bc9 Reviewed-on: https://chromium-review.googlesource.com/c/crossbench/+/3904552 Reviewed-by: Patrick Thier <pthier@chromium.org>
Crossbench is a cross-browser/cross-benchmark runner to extract performance numbers.
This project uses poetry deps and package scripts to setup the correct environment for testing and debugging.
pip3 install poetry
Example usage:
poetry run crossbench speedometer_2.0 \
--browser=/path/to/chromium \
--stories=VanillaJS.* \
--probe=profiling \
--probe=v8.log
Describe all subcommands with stories and all probes:
poetry run crossbench describe
Browsers : Interface to start, interact and stop browsers. The main implementions use selenium for maximum system independence.
Probes : Probes define a way to extract arbitrary (performance) numbers from a host or running browser. This can reach from running simple JS-snippets to extract page-specific numbers to system-wide profiling.
Stories : Stories define sequences of browser interactions. This can be simply loading a URL and waiting for a given period of time, or in more complex scenarios, actively interact with a page and navigate multiple times.