Chunking: Loading the entire input / output cube onto memory#162
Merged
Cameron-Van-Eck merged 5 commits intoCIRADA-Tools:masterfrom Dec 8, 2025
Merged
Chunking: Loading the entire input / output cube onto memory#162Cameron-Van-Eck merged 5 commits intoCIRADA-Tools:masterfrom
Cameron-Van-Eck merged 5 commits intoCIRADA-Tools:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The current behaviour of chunking is that, the complete input / output cube is not loaded onto memory (via memmap = True)
This probably makes sense for many cases (where cube size > memory available).
However, for many cases the amount of memory available may actually be enough to hold the entire cube.
For such cases, loading in the entire cube onto memory can lead to significant speed up (>> factor of 10 in speed)
It may be worthwhile having this (memmap = False) as an option to users (of course, keeping the current memmap = True as the default behaviour)