-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New chunking approach that never splits encoded chunks #11060
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
Open
jsignell
wants to merge
10
commits into
pydata:main
Choose a base branch
from
jsignell:non-splitting-auto
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsignell
commented
Dec 30, 2025
* Move ``preserve_chunks`` to base ChunkManager class * Get target size from dask config options for DaskManager * Add test for open_zarr
jsignell
commented
Dec 31, 2025
| ({"x": "preserve", "y": -1}, (160, 500)), | ||
| ], | ||
| ) | ||
| def test_open_dataset_chunking_zarr_with_preserve( |
Member
Author
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These tests are kind of slow.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
io
topic-backends
topic-hypothesis
Strategies or tests using the hypothesis library
topic-NamedArray
Lightweight version of Variable
topic-testing
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
chunks={}orchunks="auto". Since Remove special mapping ofautoto {} inopen_zarr#11010 got in xarra could eventually change the default onopen_zarrto map it to"preserve"rather than to{}if dask is available.whats-new.rstapi.rstProposal
A new
chunksoption that is only allowed to use encoded chunks or multiples of them. No chunk splitting allowed.Demo
Current behavior when
chunks="auto"This PR introduces a new option:
chunks="preserve"Context
I originally set out to update the
auto_chunksfunction in dask, but it felt like my goals were actually quite different. The goal of the daskauto_chunksfunction is to guarantee that the chunksize will be under a configurable limit while preserving the aspect ratio ofprevious_chunks(previous_chunks==encoding). This PR instead guarantees that encoded chunks are never split but it will multiply them by some factor to try to get the chunksize close to a targetsize. It doesn't try to preserve the aspect ratio of the chunks. Instead it goes after the dim where there is the greatest number of chunks and it tries to take those in bigger bites.Also:
"preserve".