AWS Lambda was already serverless, now it can be x86-less too
- Reference: 1632988625
- News link: https://www.theregister.co.uk/2021/09/30/aws_lambda_on_graviton2/
- Source link:
The server-renter on Wednesday [1]slipped out news that Gravitons are an option alongside its x86 offerings from Intel and AMD.
It will come as no surprise that AWS reckons its own silicon slays on price – the company claims Graviton2 can deliver "up to 19 percent better performance at 20 percent lower cost".
[2]
But wait: there's more! AWS asserted that "Workloads using multithreading and multiprocessing, or performing many I/O operations, can experience lower execution time and, as a consequence, even lower costs."
[3]IBM's former Chinese Power Systems partner sues for theft of customer data
[4]Russian Arm SoC now shipping in Russian PCs running Russian Linux
[5]Google is designing its own Arm-based processors for 2023 Chromebooks – report
AWS reckons it's not hard to put that claim to the test if your functions have no binary dependencies – a happy lack that will often be the case for functions written with Node.js and Python, or functions compiled to Java bytecode.
Under those circumstances the cloud colossus suggests "changing the architecture of a Lambda function is like flipping a switch". Or, to be more accurate, changing your runtime settings to select arm64 instead of x86_64 .
[6]
Serverless functions are not always lightweights that can get away with modest compute resources. Indeed, in December 2020 AWS tripled the memory it was willing to put behind Lambda functions, lifting the ceiling to 10GB of RAM and allowing half a dozen vCPUs. That spec remains an option with Graviton2, so it's not as if AWS is suggesting you run functions on just one of the Graviton2's 64 cores.
Nor is AWS restricting Graviton2 from jobs that at first blush seem best-suited to a Xeon or EPYC: the biz lets it handle heavyweight workloads including [7]databases that need 64 cores and a terabyte of RAM.
[8]
Lambda is the 25th service AWS runs on the silicon.
Amazon.com's side hustle is not alone in using Arm-powered servers to offer cheaper cloud services – [9]Oracle has done the same. Among hyperscalers, Microsoft has also shown signs of being Arm-curious. ®
Get our [10]Tech Resources
[1] 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/
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YVWK50mHcnfI194AakmZjQAAAAs&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://www.theregister.com/2021/09/13/neu_cloud_vs_ibm/
[4] https://www.theregister.com/2021/08/10/baikall_iru_arm_pcs/
[5] https://www.theregister.com/2021/09/02/google_chromebook_chips/
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YVWK50mHcnfI194AakmZjQAAAAs&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[7] https://www.theregister.com/2021/03/17/ec2_graviton_x2gd_memory_intensive/
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offprem/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YVWK50mHcnfI194AakmZjQAAAAs&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[9] https://www.theregister.com/2021/05/25/oracle_ampere_cloud/
[10] https://whitepapers.theregister.com/
Re: Serverless?
Serverless benefits the user over IaaS because it actually delivers the cloud premise of freeing them from managing OS instances. IME, that's where most of the maintenance effort goes (more than the hardware/firmware/hypervisor aspect of servers that IaaS covers, in fact).
It's generally more effort to adopt, and less interchangeable with other deployment types, but it certainly makes a difference to the amount of non-application operations effort required. It's probably what I'd choose if starting from scratch, in fact.
Re: Serverless?
If you have a function which runs only periodically, you don't need an instance running while it's inactive, potentially saving money. Because it's serverless (from the consumer point of view), you don't have the worries of patching, OS maintenance, security etc and it's highly available because AWS will just run it on whatever bit of tin is available at the time you need to run the function.
It's a niche usage, but there are some white papers/blog posts where you can effectively run an entire website using Lambda functions, so there's some useful capabilities in there.
Serverless?
Of course in reality 'serverless' is not serverless. There must be servers for the transactions to take place. It's just that the servers are transient. Obviously that can be an advantage to the provider as it reduces the amount of idle processing power across the large infrastructure (most transactions being bursty). I'm not sure what specific benefit that offers the user though.