[CI][UR] Unify UR and SYCL benchmarking CI into a single benchmarking CI #17229
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pbalcer
approved these changes
Mar 3, 2025
pbalcer
reviewed
Mar 3, 2025
Yeah: Although, I'm thinking we do this at the end, when the workflow has taken more shape and we know exactly what locations to add to CODEOWNERS |
This patch improves numerous aspects on how the benchmarking results are visualized: - rewrites the way HTML charts are generated, using a library (Chart.js) that's both easier to use and more visually pleasing. The new HTML page also now decouples data from the HTML itself, leading to faster load times and the ability to fetch data from remote sources. - The markdown output now contains a failures section that lists all benchmarks that failed for a given run. This will be a helpful for developers during PR testing. - Benchmarks can now have description that's displayed on the page. - And many more minor improvements.
…to unify-benchmark-ci
This reverts commit f79bbbf.
... and add presets to more easily
…to unify-benchmark-ci
martygrant
pushed a commit
that referenced
this pull request
Mar 24, 2025
Given that #17229 is massive, I am splitting the PR into smaller individual PRs such that reviewers would have an easier time. This PR prepares for changes in #17229 by moving the UR benchmarking scripts into devops. For more context: A previous attempt at splitting is here #17545, but even this is way too big, and thus I'm splitting it into chunks. This is a non-functional change, as these scripts not currently used anywhere right now... hopefully soon though!
RossBrunton
pushed a commit
to oneapi-src/unified-runtime
that referenced
this pull request
Mar 24, 2025
Given that intel/llvm#17229 is massive, I am splitting the PR into smaller individual PRs such that reviewers would have an easier time. This PR prepares for changes in intel/llvm#17229 by moving the UR benchmarking scripts into devops. For more context: A previous attempt at splitting is here intel/llvm#17545, but even this is way too big, and thus I'm splitting it into chunks. This is a non-functional change, as these scripts not currently used anywhere right now... hopefully soon though!
This was referenced Mar 24, 2025
sarnex
pushed a commit
that referenced
this pull request
Mar 25, 2025
This PR adds a placeholder sycl-ur-perf-benchmarking.yml in preparation for testing and merging the benchmark.yml in #17229.
martygrant
pushed a commit
that referenced
this pull request
Mar 26, 2025
…rks (#17617) This PR partially merges changes introduced in #17229. Specifically, it merges changes related to: - Introducing metadata in the result - Tweaks to the benchmarks itself: benchmarks ran, parameters used to run, what is enabled/disabled, etc - Enables/Disables benchmarks we are interested/no longer interested in - Disables non-working benchmarks - Bumps commit hashes used to fetch each benchmark - New command line arguments, such as `--build-jobs` and `--redownload` (to re-fetch the benchmarks) **Note:** I am relying on this PR having its commits squashed during merge (which should be the default behavior for intel/llvm) I did not try to clean up the commit history. Most of these changes are by Piotr anyway, I wanted to make sure he was properly credited for the changes. Updates for current splitting effort of #17229: #17545 (comment) --------- Co-authored-by: Piotr Balcer <[email protected]> Co-authored-by: Łukasz Stolarczuk <[email protected]>
This was referenced Mar 26, 2025
martygrant
pushed a commit
that referenced
this pull request
Mar 27, 2025
In continuation of the effort outlined in #17545 (comment), this PR merges further changes introduced in #17229. Specifically, it merges @pbalcer's changes for adding the ability to run different benchmarking presets **Note:** I am relying on this PR having its commits squashed during merge (which should be the default behavior for intel/llvm) --------- Co-authored-by: Piotr Balcer <[email protected]> Co-authored-by: Łukasz Stolarczuk <[email protected]>
martygrant
pushed a commit
that referenced
this pull request
Mar 27, 2025
…ntation (#17662) In continuation of the effort outlined in #17545 (comment), this PR merges further changes introduced in #17229. Specifically, it merges changes related to markdown output generation intended for creating summaries on user PRs. Note: I am relying on this PR having its commits squashed during merge (which should be the default behavior for intel/llvm) --------- Co-authored-by: Piotr Balcer <[email protected]> Co-authored-by: Łukasz Stolarczuk <[email protected]>
…7608) Beside the new class for fragmentation measurements, ComputeUMFBenchmark base class is directly replaced by GBench. Methods and attributes previously included in ComputeUMFBenchmark have been relevant only for Google Benchmark, therefore inheriting from ComputeUMFBenchmark would have been pointless for benchmarks using other frameworks. Additionally, each benchmark is run separately in order to avoid any impact of benchmarks on each other. Benchmarks using glibc are excluded from fragmentation measurements.
martygrant
pushed a commit
that referenced
this pull request
Mar 28, 2025
In continuation of the effort outlined in #17545 (comment), this PR merges further changes introduced in #17229. Specifically, it merges @pbalcer's new HTML benchmarking results dashboard implementation, which now loads html data from remote sources in order to facilitate bringing up the benchmarking dashboard in intel.github.io in the future. **Note:** I am relying on this PR having its commits squashed during merge (which should be the default behavior for intel/llvm) I did not try to clean up the commit history. Most of these changes are by Piotr anyway, I wanted to make sure he was properly credited for the changes. --------- Co-authored-by: Piotr Balcer <[email protected]> Co-authored-by: Łukasz Stolarczuk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unfortunately this PR got pretty big, and people have expressed that they don't want to review such a big PR...
I am working on splitting this PR, see this for current status: #17545 (comment)