Fixed disk trashing on input cube reads. Fixes #3711 #4793
Merged
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.
Fixes very slow run times when using band priority.
Description
The band priority mode has to read extra data (i.e., the band used to set the priority). The default cube IO caching algorithm was causing Cube IO cache memory to be flushed too soon. Resulting in multiple reads of the same data, aka thrashing. The change shows automos to run 13 times faster than before with no difference in output values.
Related Issue
#3711
Motivation and Context
Unnecessarily slow execution when using band priority
How Has This Been Tested?
All existing tests pass locally. Hand testing shows the band priority option running 13 times faster. There are no timing test in the test suite.
Screenshots (if appropriate):
Types of changes
Checklist:
Licensing
This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words: