-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Workers should adjust BLAS/LAPACK/Numpy threads #230
Comments
Absolutely. There is work happening already in dask/distributed#4377 to address this. |
@jacobtomlinson please correct me if I'm wrong, does dask/distributed#4377 really address this issue? Looking briefly into that, it seems like it's more about the number of Dask processes and thread but not the BLAS/LAPACK/Numpy threads? |
Ah right I see, I misunderstood the request. Most cluster managers support an |
@jacobtomlinson thanks for prompt response. I understand, but do you think |
That's is definitely a possibility. I'm not sure whether we do this in any other cluster managers. Perhaps someone else from @dask/maintenance might know? |
Sounds like another point where spec-cluster might be able to give a consolidated view over different deployment types - like how many CPU cores are available to each worker, possibly different than the number of threads requested. I suspect, though, that in most cases setting all the threading options to 1 is the right thing to do. |
Should workers by default adjust BLAS/LAPACK/Numpy threads as per dask-best-practices? Since we have access to the number of threads/workers and cores, it should be possible adjust those accordingly. wdyt?
The text was updated successfully, but these errors were encountered: