Support for 'maxColSizeMb' autoscaling config parameter #114
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
|
Hey thanks for the PR (and sorry for the wait). I think this is a bit too granular for ClusterODM to have and I'm not sure filesize is a universal predictor of memory usage so I will opt not to merge this, but I'm glad you were able to modify ClusterODM to fit your organization's needs. 🙏 |
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.
Allows for an additional optional autoscaling configuration parameter 'maxColSizeMb', which defines the total size of the collection to be processed. This was identified as a useful parameter particularly for high resolution imagery, given that the size of individual images can be as large as 20 or 30 MB per file and subsequently take up a lot more memory on the processing node.