EDSC-4312: Bumping lambda memory for adminGetPreferencesMetrics
#1833
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.
Overview
What is the feature?
Bump memory for the lambda so that it completes in production. The database is large enough in production that as is, the job cannot complete so we aren't getting the page to load. See
https://search.earthdata.nasa.gov/admin/preferences-metrics
. We know that that at least256mb
was sufficient because we tried this on AWS console and re-ran the lambda. however, bumping this up keeps us from needing to update this again in the near future. Cost is not an issue here this lambda is only run by our internal team sparingly and might reduce costs since the actual execution time will be diminished.What is the Solution?
Bumping up the resources for this sparingly called lambda function
What areas of the application does this impact?
Admin page aws-lambda memory
Testing
Reproduction steps
Attachments
Please include relevant screenshots or files that would be helpful in reviewing and verifying this change.
Checklist