You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a follow-up to adding performance benchmark tests (#4105). In order for benchmark tests to provide value, it is important to track changes in performance over time.
Short description of the changes
This adds a Github workflow that runs all benchmark tests and publishes results to Github pages. This is similar to what the Collector is already doing here.
The PR is in a draft mode until self-hosted runner is available to this repo (the process of adding a self-hosted runner is progress).
Type of change
New feature (non-breaking change which adds functionality)
How Has This Been Tested?
The workflow has been tested in a fork. Here is a page with charts that it has generated.
Merging #4144 (fecd2b0) into main (52f428a) will decrease coverage by 0.21%.
The diff coverage is n/a.
❗ Current head fecd2b0 differs from pull request most recent head 8102aae. Consider uploading reports for the commit 8102aae to get more accurate results
@pichlermarc Thanks for the review. There is potentially one more change that I am wondering about - should we run this on release or on every merge to main? With merge to main, it would be easier to catch regressions. What do you think?
@pichlermarc Thanks for the review. There is potentially one more change that I am wondering about - should we run this on release or on every merge to main? With merge to main, it would be easier to catch regressions. What do you think?
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
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.
Which problem is this PR solving?
This is a follow-up to adding performance benchmark tests (#4105). In order for benchmark tests to provide value, it is important to track changes in performance over time.
Short description of the changes
This adds a Github workflow that runs all benchmark tests and publishes results to Github pages. This is similar to what the Collector is already doing here.
The PR is in a draft mode until self-hosted runner is available to this repo (the process of adding a self-hosted runner is progress).
Type of change
How Has This Been Tested?
The workflow has been tested in a fork. Here is a page with charts that it has generated.