5 ms·
This seems pretty huge ('19% better performance at 20% lower cost') considering many (most?) Lambda workloads will be arch-agnostic, not even needing updated sc
by OJFord 5y ago
This seems pretty huge ('19% better performance at 20% lower cost') considering many (most?) Lambda workloads will be arch-agnostic, not even needing updated scripts/installed libs etc. Then many more will only need a trivial re-compile.
I'm sure they don't need me to tell them they'll be inundated with demand...
- orf 5y agoIt will probably take a while to ramp up - it's explicitly opt-in and I expect there's a huge amount of existing code that creates lambdas without being able to specify the architecture. For starters example Terraform and Cloudformation don't support it yet. And if you're using a 3rd party layer you need to wait for them to publish a layer that explicitly supports that architecture.
- k__ 5y agoAccording to AWS, CFN rollout is happening right now.
- orf 5y agoSure but then you have the CDK, etc. I’d be interested to know how many people create lambdas in the console and not via some Other tooling, which needs to be updated to support this.
- OJFord 5y agoGood point. I'd forgotten memory was the only existing toggle (i.e. no variation of x86 CPUs as on EC2, that 'g' or whatever could just be added to).
- smoldesu 5y agoPrecisely. Once you start to consider how other ISAs factor into that (like perhaps RISC-V on the horizon) I really wonder if ARM has a chance to take off in the first place. A ~50% price/performance boost isn't negligible, but it's also not very compelling. Especially for larger companies who'd need to invest more time/money into transitioning their backend.
- rewma 5y ago> A ~50% price/performance boost isn't negligible, but it's also not very compelling. My take is that a 50% discount in price/performance and a 20% discount in price per execution unit that's only a toggle flip away is something that everyone loves and is eager to jump onboard. The only exception is when your workload stubbornly stays within free tier limits, which in that case you have no compelling reason to do the work.
- staticassertion 5y ago50% price/performance is very compelling. If you talk to a large company and say "you can cut your compute bill in half with a single re-deploy" they will be very happy.
- paranoidrobot 5y agoTerraform issue tracking support for architectures parameter: https://github.com/hashicorp/terraform-provider-aws/issues/21090 https://github.com/hashicorp/terraform-provider-aws/issues/2... There's a pull request that went up about 40 minutes prior to my comment. So it looks like it's coming, soon.
- reilly3000 5y agoPulumi has theirs up already: https://www.pulumi.com/blog/aws-lambda-functions-powered-by-graviton2/ https://www.pulumi.com/blog/aws-lambda-functions-powered-by-...
- rewma 5y ago> This seems pretty huge ('19% better performance at 20% lower cost') I believe the performance boost will not be meaningful and the only important factor is cost per GB*s, given that most Lambda workloads are IO bound or simple event handlers that barely take 1s to run anyway. Nevertheless this is exciting stuff, specially given that NodeJS might be lambda's most popular runtime and thus we might only be a toggle flip away from a 20% discount.
- ryanmarsh 5y agoMy Lambda workloads are CPU bound so this is great but I get it, most spend their time waiting for IO.
- diskzero 5y agoI wrote a lambda that encoded a timeline comprised of audio, video and GLSL shaders using SwiftShader and ffmpeg. Time to give it try again!
- bonobocop 5y agoApparently Python rules the roost for Lambda: https://mobile.twitter.com/julian_wood/status/1442775542374277120/photo/1 https://mobile.twitter.com/julian_wood/status/14427755423742... But NodeJS is second!
- zxcvbn4038 5y agoGolang is the top dog for Lambda IMO. The AWS Lambda SDK for Golang includes the entire lambda runtime so you can deploy a single 20mb binary w/ an Alpine linux base (speaking of the ECR backed lambdas) and that’s it. With NodeJS you either have to use the AWS provided centos based images which weigh in at several hundred MB or do some multistage magic to build a minimal Alpine image including the lambda runtime and AWS SDK which altogether still weighs in almost a hundred MB.
- bonobocop 5y agoTBH, as the Dockerfile based Lambda layers have a 20GB file size limit, I'm not sure the size matters as much. It's certainly easier to figure out what's going on in a smaller container though! I've had to debug some nasty situation with layers in Python Lambdas before and it's not fun...