-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
MAINT Adapt scheduling of PairwiseDistancesRadiusNeighborhood
#22829
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
MAINT Adapt scheduling of PairwiseDistancesRadiusNeighborhood
#22829
Conversation
Your dataset is generated uniformly. I'd expect that in that case all tasks should be roughly the same and 'static' being overprforming. Could you run the same benchmark with a dataset with non-uniform density, i.e. regions with high density and regions with low density ? |
|
Using bigger dataset ( ResultsmainRaw results
bce219eRaw results
Since it scales similarly to |
So no significant difference even for non-uniform distances. +1 for using static to make the execution more deterministic between machine with different number of threads by avoid non-commutative rounding errors in the reduction operations. |
Also the benchmarks are a little bit in favor of "static" so I'm +1 as well |
Reference Issues/PRs
Follow-up of #22320
What does this implement/fix? Explain your changes.
Test various configuration of scheduling for OpenMP and pick the best one using this script with mimalloc.
Results
main
Raw results
bce219e
Raw results