-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Unrelated updates in overlay with dmap triggers computation of another dmap #6135
Comments
I was a little surprised, the caching on the So based on that everything is working correctly here, so I think the only real fix to apply here is to warn users that if they pass a non-persisted Dask backed array to rasterize/regrid then the interactive performance will be significantly degraded. Alternatively |
Some timings, indicating it's pretty much entirely range calculations. No
|
I think this would be ideal since
Is not possible in some cases if the data is much larger |
Unfortunately I found this to effectively make zero difference. |
@philippjfr, is there a potential solution for a larger non-persisted Dask-backed array to make use of rasterize in this context? |
If this is loaded, things move much quicker
The text was updated successfully, but these errors were encountered: