perf: Delete OMP in torontonian calculations #366
Merged
Conversation
This file contains 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
There seems to be a too big OMP overhead in the torontonian calculations, at least for smaller system sizes. It could be solved by coming up with a smarter schedule. For now, OMP is deleted from the code. Moreover, some related benchmarks got updated.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #366 +/- ##
==========================================
- Coverage 97.78% 97.44% -0.35%
==========================================
Files 72 72
Lines 3842 3838 -4
==========================================
- Hits 3757 3740 -17
- Misses 85 98 +13 ☔ View full report in Codecov by Sentry. |
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.
There seems to be a too big OMP overhead in the torontonian calculations, at least for smaller system sizes. It could be solved by coming up with a smarter schedule. For now, OMP is deleted from the code.
Moreover, some related benchmarks got updated.