Move to Arm64 lambdas #884
Merged
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
akash1810
force-pushed
the
aa/arm64
branch
6 times, most recently
from
0d5688d to
9fb74b2
Compare
akash1810
commented
Mar 27, 2024
| @@ -1,7 +1,7 @@ | |||
| generator client { | |||
| provider = "prisma-client-js" | |||
| previewFeatures = ["views"] | |||
| binaryTargets = ["native", "rhel-openssl-3.0.x"] | |||
| binaryTargets = ["native", "linux-arm64-openssl-3.0.x"] | |||
There was a problem hiding this comment.
| @@ -12,4 +13,26 @@ describe('The ServiceCatalogue stack', () => { | |||
| const template = Template.fromStack(stack); | |||
| expect(template.toJSON()).toMatchSnapshot(); | |||
| }); | |||
|
|
|||
| it('only uses arm64 lambdas', () => { | |||
There was a problem hiding this comment.
This test should help enforce usage of arm64 based lambdas.
With the same duration, and memory usage Arm64 is 20% cheaper than x86_64. The "worst" change is to the github-actions-usage lambda, which sees a 19.08% duration increase. Given these lambdas don't have need to complete in a given timeframe, I think this change is acceptable. Whilst it'll take longer, the Arm64 version will cost ~16% less1. Footnotes
|
Arm based lambdas are cheaper and more performant. See https://aws.amazon.com/blogs/aws/aws-lambda-functions-powered-by-aws-graviton2-processor-run-your-functions-on-arm-and-get-up-to-34-better-price-performance/.
NovemberTang
approved these changes
Mar 28, 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.
What does this change?
Change the architecture of each lambda to Arm64.
Why?
Arm based lambdas are cheaper and more performant. See https://aws.amazon.com/blogs/aws/aws-lambda-functions-powered-by-aws-graviton2-processor-run-your-functions-on-arm-and-get-up-to-34-better-price-performance/.
How has it been verified?
Statistics
Here are some statistics after invoking the x86_64 and arm64 versions of each lambda once with the same input.
As mentioned in the linked post:
In this estimate1 of 100,000 requests per month, of 50,000ms duration, and 1,024MB memory, Arm64 costs $61.33 and x86_64 $76.67.
That is, whilst the statistics do not suggest a dramatic change in performance, we will see a reduction in the bill.
Footnotes
URL will expire in 1 year. ↩