Skip to content
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.

Sign up for GitHub

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

Jump to bottom

cf.aggregate sometimes needlessly puts in a "transpose" layer into the Dask graph #754

Closed
davidhassell opened this issue Apr 3, 2024 · 0 comments · Fixed by #755
Closed

cf.aggregate sometimes needlessly puts in a "transpose" layer into the Dask graph #754

davidhassell opened this issue Apr 3, 2024 · 0 comments · Fixed by #755
Labels
active storage Relating to active storage operations bug Something isn't working performance Relating to speed and memory performance
Milestone
3.16.2

Comments

@davidhassell
Copy link
Collaborator

davidhassell commented Apr 3, 2024 •
edited
Loading

In v3.16.2, cf.aggregate sometimes needlessly puts in a "transpose" layer into the Dask graph that is a null operation, i.e. it doesn't change the axis order. This can have performance implications (it is slower to inspect and optimise a Dask graph with more layers), and prevents the possibility of active storage operations (see #501).

PR to follow
@davidhassell davidhassell added bug Something isn't working performance Relating to speed and memory performance active storage Relating to active storage operations labels Apr 3, 2024
@davidhassell davidhassell added this to the Next release milestone Apr 3, 2024
@davidhassell davidhassell mentioned this issue Apr 3, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
active storage Relating to active storage operations bug Something isn't working performance Relating to speed and memory performance
Projects
None yet
Milestone
3.16.2
1 participant
@davidhassell