Increases max memory for TI version only of fim-data-prep Lambda #975
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
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.
Refs #938
The apocalyptic testing uses a lot more resources, as expected. In this case, the fim-data-prep Lambda was failing when running the srf_max_inundation. Rather than increase the memory for this Lambda across the board, this PR adds code to only increase it for the TI environment, since we'll assume that apocalyptic conditions should not ever be reached in real life. We want to continue to ensure everything can possibly be run within the allowable, configurable limits within the TI environment.