Increase memory and timeout configuration for the transform lambda #64
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
We started seeing out of memory errors in the transform lambda when onboarding the variant-nowcast-hub. This is the first time we've onboarded a hub to S3 that includes sample data, and it looks like the default memory allocation of 128MB isn't sufficient. For example, a single UMass submission is 27MB in memory after the parquet file is read by pyarrow. We can and should investigate ways to make the transform process better about memory, but let's increase the memory now to ensure we're in a good place until then.
|
🍹 The Update (preview) for hubverse/hubverse-aws/hubverse was successful. Resource Changes Name Type Operation
~ hubverse-transform-model-output aws:lambda/function:Function update
|
🍹
|
bsweger
commented
Nov 15, 2024
| @@ -169,7 +169,8 @@ def create_transform_lambda( | |||
| s3_bucket=s3_bucket, | |||
| s3_key=s3_key, | |||
| tags={"hub": "hubverse"}, | |||
| timeout=210, | |||
| memory_size=500, | |||
There was a problem hiding this comment.
500 = 500 MB
600 = 600 seconds
nickreich
approved these changes
Nov 15, 2024
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.
Addresses hubverse-org/hubverse-transform#32
We started seeing out of memory errors in the transform lambda when onboarding the variant-nowcast-hub. This is the first time we've onboarded a hub to S3 that includes sample data, and the default memory allocation of 128MB isn't sufficient.
For example, a single UMass submission is 27MB in memory after the parquet file is read by pyarrow. We can and should investigate ways to make the transform process better about memory, but let's increase the memory now to ensure we're in a good place until then.