Implement dynamic memory allocation for multi-frame AutoRIFT jobs #3018
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
cmspeed
force-pushed
the
coseis-autorift
branch
from
1780d15 to
124e037
Compare
cmspeed
force-pushed
the
coseis-autorift
branch
from
124e037 to
d46c192
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR updates the
AUTORIFTjob-type memory allocation logic to support multi-frame processing (e.g., earthquake coseismic displacement jobs covering large surface ruptures) without requiring a new job type.Key Changes
Sentinel-2 jobs containing more than 4 frames (in either
referenceorsecondary) are now allocated 16GB memory. Sentinel-2 jobs containing 4 or fewer frames remain at 8GB.Replaced sensor-specific memory constants (e.g.,
AUTORIFT_S2_MEMORY) with general, capacity-based tiers (e.g.,AUTORIFT_MEMORY_8GB,AUTORIFT_MEMORY_16GB,AUTORIFT_MEMORY_32GB).Pre-existing memory allocation remains unchanged, with the exception of name changes to memory allocation constants (see above bullet). Specifically, single-frame Landsat jobs and all Sentinel-1 jobs default to 16GB and 32GB, respectively.