Repository navigation
Add num_chunk_per_batch to job kwargs and use it for zarr v3 shard writes
#4833
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
samuelgarcia
wants to merge
12
commits into
SpikeInterface:main
Choose a base branch
from
samuelgarcia:parallel_executor_grouped_chunks
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.
+131
−35
Open
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
218b394
draft proof of concept of num_chunk_per_batch for the zarr shards
samuelgarcia d7a6e96
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 9bba81b
fix: add num_chunk_per_batch to job_keys
alejoe91 dafb095
fix: failing tests
alejoe91 194289b
fix: conflicts
alejoe91 c07303b
fix: serialization tests
alejoe91 29f083c
fix: serialization tests 2
alejoe91 dcfeb47
fix: serialization tests 3
alejoe91 d7fc836
feat: use num_chunk_per_job in sharding and add tests
alejoe91 b4e4bed
fix: batches should not cross segments!
alejoe91 18c0bf1
Merge branch 'main' into parallel_executor_grouped_chunks
alejoe91 8502e8a
typos from Chris
alejoe91 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
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.
Since this is so zarr specific, is it better to give it a more specific name for the use case, like
num_chunk_per_shard?Also, my feeling is that this is mostly for internal use and we don't expect users to pass it? I.e. if you're using sharding, we compute
num_chunk_per_batchfor you. Maybe this should be private or documented as an "internal job kwargs" or somethingThere 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.
I don't think it's zarr specific. There might be other instances where you might want jobs to loop through chunks (I still have to think of one though hehehe)
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.
Ok, so a user can set
num_chunk_per_batchand this does affect saving binary files etc. But for non-zarr stuff, it shouldn't change memory use?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.
I think this is zarr specific. In #4905 I argue that what we need is to be able to separate the chunk size (in time) of the different steps of a processing chain. But I do think that the way it is solved here is very zarr specific because each call still gets a single chunk. What a batch adds is that one worker owns a range of consecutive chunks and that only matters when several chunks share one storage object. Right now only zarr shards do that.
I left a general comment with a way to get that ownership inside the zarr writer without a new job kwarg.