DBSCAN Documentation (suggestions for parallel processing) #3879
Labels
Comments
|
Why not, PR welcome :) |
|
Is adding a n_jobs parameter a reasonable option? On 25 November 2014 at 09:15, Andreas Mueller [email protected]
|
|
This looks fixed as dbscan now accepts n_jobs. |
|
parameter n_jobs seems ignored. it makes no difference |
|
in master it is not ignored. in 0.19.1 it is ignored unless
algorithm='brute'
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think it is worth adjusting the DBSCAN documentation to note that if you ask DBSCAN to calculate pairwise distances for you, then it will do so using only one core.
If you want to take advantage of multiple cores, you should pre-calculate a distance matrix using
pairwise_distances(n_jobs=)and then run DBSCAN with your pre-calculated distance matrix.The text was updated successfully, but these errors were encountered: