Skip to content

Commit 1fef4e2

Browse files
authored
Merge pull request #1949 from pbalcer/ci-benches
add info how to run benchmarks in CI
2 parents 2d3524e + ca68aca commit 1fef4e2

File tree

2 files changed

+16
-0
lines changed

2 files changed

+16
-0
lines changed

scripts/benchmarks/README.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,22 @@ This will download and build everything in `~/benchmarks_workdir/` using the com
1515

1616
The scripts will try to reuse the files stored in `~/benchmarks_workdir/`, but the benchmarks will be rebuilt every time. To avoid that, use `-no-rebuild` option.
1717

18+
## Running in CI
19+
20+
The benchmarks scripts are used in a GitHub Actions worflow, and can be automatically executed on a preconfigured system against any Pull Request.
21+
22+
![compute benchmarks](workflow.png "Compute Benchmarks CI job")
23+
24+
To execute the benchmarks in CI, navigate to the `Actions` tab and then go to the `Compute Benchmarks` action. Here, you will find a list of previous runs and a "Run workflow" button. Upon clicking the button, you will be prompted to fill in a form to customize your benchmark run. The only mandatory field is the `PR number`, which is the identifier for the Pull Request against which you want the benchmarks to run.
25+
26+
You can also include additional benchmark parameters, such as environment variables or filters. For a complete list of options, refer to `$ ./main.py --help`.
27+
28+
Once all the required information is entered, click the "Run workflow" button to initiate a new workflow run. This will execute the benchmarks and then post the results as a comment on the specified Pull Request.
29+
30+
By default, all benchmark runs are compared against `baseline`, which is a well-established set of the latest data.
31+
32+
You must be a member of the `oneapi-src` organization to access these features.
33+
1834
## Requirements
1935

2036
### Python

scripts/benchmarks/workflow.png

213 KB
Loading

0 commit comments

Comments
 (0)