-
Notifications
You must be signed in to change notification settings - Fork 43
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
Why we need to set dask to single tread? #233
Comments
Thanks for the report! Salem has been in a maintenance-only mode since quite a while now, I wouldn't be surprised if a lot of the code is not up-to-date with dask/xarray standards... |
@singledoggy is there anything we can do here? I'll release a maintenance update soon, it might be a moment to tackle this.... |
Sorry for the late reply. I must clarify that my expertise in dask is limited, and therefore, the suggestions provided may not be entirely accurate. I notice that the HDF5 library was not thread safe , so it's wise to set But maybe it's better to temporarily set configuration values within a context manager?
|
And I'm not sure if it's a good way to set |
I've noticed force single threaded mode #39
And it may has someting to do with #37
Currrently I tend to use
so this setting may change the default config and can't work with my current workflow.
And in my case, If i comment the
dask.config.set(scheduler='single-threaded')
, I didn't meet any error when loading data byI'll do more tests when I have time.
The text was updated successfully, but these errors were encountered: