Use TeamPolicy
in Details::expandHalfToFull
to improve performance
#811
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.
In #809 we had opted to merge in the version with
RangePolicy
even though it was commented out with a macro guard in the code I was using to measure performance.I don't have numbers handy to share but with the
TeamPolicy
version, findHalfNeighborList+expandHalfToFull is 15% faster than the "classic" BVH query implementation, with aRangePolicy
it is slower than the current status quo.