Increased execution memory for GCHP cloud benchmarks from 80 GB to 120 GB #471
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.
Name and Institution (Required)
Name: Bob Yantosca
Institution: Harvard + GCST
Describe the update
This is the companion PR to #470. We have increased the execution memory setting from 80 GB to 120 GB in GCHP cloud benchmarks. The CEDS emissions at 0.1 degree resolution have increased the memory footprint of the GCHP fullchem benchmark simulations.
Expected changes
This is a zero-diff update. It should now allow GCHP 1-month and 1-hour benchmarks on AWS to proceed without failing (and having to manually resubmit with more memory).
Related Github Issue