-
Notifications
You must be signed in to change notification settings - Fork 25
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
🎨 Slightly faster ClusterComplete #664
base: main
Are you sure you want to change the base?
🎨 Slightly faster ClusterComplete #664
Conversation
Signed-off-by: GitHub Actions <[email protected]>
…omplete' into efficient-single-threaded-clustercomplete
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #664 +/- ##
=======================================
Coverage 98.38% 98.38%
=======================================
Files 254 254
Lines 41149 41202 +53
Branches 1870 1878 +8
=======================================
+ Hits 40485 40538 +53
Misses 664 664
Continue to review full report in Codecov by Sentry.
|
clang-tidy review says "All clean, LGTM! 👍" |
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.
clang-tidy made some suggestions
The latest commit fixes an issue in setting the parameters that made it so that the validity witness parameters were both set to |
Description
The main goal of this PR was to re-introduce the original ClusterComplete unfolding, only to run when running on a single thread. After a lot of benchmarking, it was found, however, that the runtime improvement---somehow---is absolutely marginal. Apparently the overhead from the threading is not too great, which is also good news in a way. In the process, I found one deep copy that was performed twice in one statement (
clustering_state_for_thieves = sidb_clustering_state{clustering_state};
performed a copy construction and then a copy assignment).Unfortunately, this PR does not deserve the ⚡ label, so 🎨 is more appropriate.
Checklist: