-
-
Notifications
You must be signed in to change notification settings - Fork 361
fix/shard iteration redux #3422
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests.
Additional details and impacted files@@ Coverage Diff @@
## main #3422 +/- ##
===========================================
- Coverage 94.92% 61.07% -33.86%
===========================================
Files 79 79
Lines 9500 9500
===========================================
- Hits 9018 5802 -3216
- Misses 482 3698 +3216
🚀 New features to boost your workflow:
|
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.
Note: we don't actually need one get per shard, but this is the current behavior
Could you open an issue to track this?
#3421 tracks this |
Completes the work of #3299 by replacing a second invocation of
_iter_chunk_coords
with_iter_shard_coords
.In a separate PR, we need to refactor this code block:
zarr-python/src/zarr/core/array.py
Lines 4402 to 4428 in b8dbf56
I add a test that checks how many
get
requests we make when callingcreate_array(data=..)
. Inmain
, it's 1get
per chunk (bad). In this PR, it's 1get
per shard (better). But we can also get to 0get
s per shard by introducing some special logic for full shard writes. expect this in a later PR.edit: closes #3169 and #3421