-
Notifications
You must be signed in to change notification settings - Fork 3
perf: speed up BroadcastTask with z-chunking & caching #72
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
macrintr
wants to merge
9
commits into
main
Choose a base branch
from
tmacrina-broadcast-z-cache
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.
Open
Changes from 6 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
34ae977
Add mip classmethods for PyramidDistanceFieldSet
macrintr 13e001f
Add caching to BroadcastTask
macrintr 7299b39
Add --broadcast_chunk_z to align
macrintr a311839
Format mipless_cloudvolume.py
macrintr 64d7809
Add set_param to MiplessCloudVolume
macrintr f635149
Set cache on during BroadcastTask
macrintr aa2ef86
Add get_param to MiplessCloudVolume
macrintr dac3265
Restore initial cache value after BroadcastTask
macrintr ecb6da6
Skip caching in BroadcastTask if chunk_z == 1
macrintr 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
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.
If you have to temporarily override a setting for an input field in-place, you should ideally keep track of the original value(s) and ensure they always are correctly restored. Right now, if the user passed the fields already with cache=True, and the function succeeds, cache will suddenly be set to False. Conversely, if the user passed the fields with cache=False, but the broadcasting fails for whatever reason, the fields will suddenly stay at cache=True after the exception got handled outside.
Is it necessary to enforce caching here, rather than leaving it to the user? I could imagine that in the special case of chunk_z=1, caching might actually be slower?
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 overrode the cache value based on feedback from @supersergiy. I agree that restoring the user's original cache value for a CloudVolume is a better practice -- see new commits. Fair point that caching would degrade performance for chunk_z == 1 -- fixed in new commit.