-
-
Notifications
You must be signed in to change notification settings - Fork 330
Group and Array repr performance #132
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
Labels
performance
Potential issues with Zarr performance (I/O, memory, etc.)
release notes done
Automatically applied to PRs which have release notes.
Milestone
Comments
Also there are two pain points for
|
Should be straightforward to fix, by setting |
Closed
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
performance
Potential issues with Zarr performance (I/O, memory, etc.)
release notes done
Automatically applied to PRs which have release notes.
Generating a repr for a group can currently be slow, for the quirky reason that the repr needs to decide if the
chunk_store
is different to thestore
in order to generate an extra line showing the chunk store if different, and this triggers a complete comparison of store contents if the store is a shelve. E.g.:There should be a way to avoid this comparison, at least in the case where
chunk_store
is None when the Group is instantiated, because then it is known there is no separate chunk store.The text was updated successfully, but these errors were encountered: