[scikit-learn] KNearestNeighbour is not running in multithread
shane.grigsby at colorado.edu
Tue May 30 15:42:51 EDT 2017
Also, I've found that nearest neighbors are often faster using a single
core given the overhead that multiprocessing brings... If you're doing a
single query over billions or more of points, parallel is faster, but if
you are doing lots of neighbor queries over hundreds of thousand or a
few million points, the single threaded call will be faster.
On 05/30, Gael Varoquaux wrote:
>You need to set the n_jobs parameter of the KNearestNeighbour object.
>scikit-learn mailing list
>scikit-learn at python.org
*PhD candidate & Research Assistant*
*Cooperative Institute for Research in Environmental Sciences (CIRES)*
*University of Colorado at Boulder*
More information about the scikit-learn