Memory fix #23
Merged
Memory fix #23
Conversation
This file contains 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
added 3 commits
December 16, 2024 18:46
…dentally) generated which is extremely memory intensive and not fully parallelized, now, dask arrays are immediately generated after reading in the image, which reduces memory burden and allows dask to use lazy loading
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changed logic of image Dask Array creation
Addresses issues in #4
Before:
_chunk_factory: Read in tiles as numpy arrays (delayed)This led to the issue that tiles were loaded into memory and persisted, leading to extremely high memory utilization
Now:
dask.arrayright away in_chunk_factory. Use delayed paradigm for parallelizationThis led to a significant speed up and hopefully to better memory management.