Skip to content

Commit a3f2b4d

Browse files
committed
Update benchmark script readme to reflect current state
1 parent c58407b commit a3f2b4d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

devops/scripts/benchmarks/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,8 @@ By default, the benchmark results are not stored. To store them, use the option
3737

3838
You can compare benchmark results using `--compare` option. The comparison will be presented in a markdown output file (see below). If you want to calculate the relative performance of the new results against the previously saved data, use `--compare <previously_saved_data>` (i.e. `--compare baseline`). In case of comparing only stored data without generating new results, use `--dry-run --compare <name1> --compare <name2> --relative-perf <name1>`, where `name1` indicates the baseline for the relative performance calculation and `--dry-run` prevents the script for running benchmarks. Listing more than two `--compare` options results in displaying only execution time, without statistical analysis.
3939

40-
Baseline_L0, as well as Baseline_L0v2 (for the level-zero adapter v2) is updated automatically during a nightly job. The results
41-
are stored [here](https://oneapi-src.github.io/unified-runtime/performance/).
40+
Baseline_PVC_L0 is updated automatically during a nightly job. The results
41+
are stored [here](https://intel.github.io/llvm/benchmarks/).
4242

4343
## Output formats
4444
You can display the results in the form of a HTML file by using `--ouptut-html` and a markdown file by using `--output-markdown`. Due to character limits for posting PR comments, the final content of the markdown file might be reduced. In order to obtain the full markdown output, use `--output-markdown full`.

0 commit comments

Comments
 (0)