FEA Introduce PairwiseDistances
#1
Closed
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.
Reference Issues/PRs
Towards scikit-learn#23958
What does this implement/fix? Explain your changes.
This simplifies the original implementation of
PairwiseDistance
by @jjerphan, with the following differences:PairwiseDistance{32,64}
doesn't subclassBaseBaseDistancesReduction{32,64}
anymore._parallel_on_{X,Y}
methods toPairwiseDistance{32,64}
, since these methods are decorated with@final
inBaseBaseDistancesReduction{32,64}
and thus can't be overwritten.chunk_size = 1
, as proposed by @ogrisel in this comment.Following this benchmark, we found that this PR yields a significant performance regression when
n_jobs = 1
and an improvement whenn_jobs > 1
, for both euclidean and manhattan distances:Any other comments?
As suggested by @jjerphan, decorating
DistanceMetric
subclasses with@final
could alleviate some of the overhead and make this implementation competitive withmain
whenn_jobs=1
.