-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continous Benchmarking Action #1137
Conversation
Thank you for the PR! |
1 similar comment
Thank you for the PR! |
Codecov Report
@@ Coverage Diff @@
## main #1137 +/- ##
==========================================
+ Coverage 91.79% 91.81% +0.01%
==========================================
Files 72 73 +1
Lines 10497 10518 +21
==========================================
+ Hits 9636 9657 +21
Misses 861 861
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Thank you for the PR! |
Thank you for the PR! |
10 similar comments
Thank you for the PR! |
Thank you for the PR! |
Thank you for the PR! |
Thank you for the PR! |
Thank you for the PR! |
Thank you for the PR! |
Thank you for the PR! |
Thank you for the PR! |
Thank you for the PR! |
Thank you for the PR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review for PR #1137 "Continuous Benchmarking Action"
This PR adds the possibility of continuous performance monitoring to Heat and therefore it is a highly valuable contribution to the overall functionality.
As far as I understand, there are three main changes coming along with this PR: First, those things required for the actual continuous benchmarking (including examples covering clustering and linear algebra); second, the "old" benchmarks have been moved to make place for the "new" continuous benchmarks; third, the unit tests for clustering have been cleaned up by introducing a dedicated function for creating the spherical test data set that now can also be used for benchmarking purposes.
As far as I can judge, the code is correct and implements the desired functionality. Since the CI runs through, I recommend merging.
… 'run bench' comment
d16523f
to
dee3a77
Compare
Thank you for the PR! |
run bench |
Thank you for the PR! |
Thank you for the PR! |
…d 'old' benchmarking folder to '2020'
Thank you for the PR! |
1 similar comment
Thank you for the PR! |
Thank you for the PR! |
Thank you for the PR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @JuanPedroGHM , this is really helpful.
One general comment: it isn't obvious to me how to view the benchmark results once the Action has run.
Otherwise I only have tiny changes requests and am looking forward to merge. Thanks a lot!
.github/workflows/benchmark_main.yml
Outdated
uses: actions/checkout@v3 | ||
- name: Setup MPI | ||
uses: mpi4py/setup-mpi@v1 | ||
- name: Use Python 3.8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shall we take 3.9 or 3.10?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll change both of them to python 3.10
.github/workflows/benchmark_pr.yml
Outdated
- name: Use Python 3.8 | ||
uses: actions/setup-python@v4 | ||
with: | ||
python-version: 3.8 # Perun only supports 3.8 and ahead |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3.9 or 3.10?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
About the link to the benchmarks, I will add a new badge to the README that points to the plots.
.github/workflows/benchmark_pr.yml
Outdated
jobs: | ||
benchmark-pr: | ||
name: Benchmark PR | ||
if: contains(github.event.pull_request.labels.*.name, 'PR talk') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's have a dedicated label, "benchmark PR" or something? Would make it more intuitive esp. for future contributors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea!
…pointing to the benchmarks, changed trigger tag
Thank you for the PR! |
1 similar comment
Thank you for the PR! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wonderful, thanks a lot @JuanPedroGHM !
Description
Enables performance tracking of HeAT by using Action for Continuous Benchmarking
Issue/s resolved: #
Changes proposed:
Type of change
Performance
Due Diligence
Does this change modify the behaviour of other functions? If so, which?
no