Limit lambda memory to 2x-3x that observed used in logs #127
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
Pull request type
Please check the type of change your PR introduces:
Reduce costs by reducing the memory allocated for lambda use
What is the current behavior?
We over-provision the executor and postprocessor lambdas with ~3GB of memory
Issue Number: N/A
What is the new behavior?
The executor and postprocessor lambdas are only provisioned with ~2x the memory they have been observed using, saving costs.
Does this introduce a breaking change?
Other information