More detailed breakdown from AWS's James Beswick: https://acloudguru.com/blog/engineering/building-more-cost-e...
AWS Lambda pricing now per ms
11–20 of 291 posts
Re: AWS Lambda pricing now per ms
#12I've learned that AWS pricing tends to improve over time, and I appreciate it. I just recently switched from a startup offering authorization to AWS Cognito because the startup kept raising their price(s). It's nice to see this drop, though I'm sure Amazon does it due to competition as well.
This is an analysis from 2018ish - https://www.stayclassyinternet.com/articles/investigating-AW...
Re: AWS Lambda pricing now per ms
#13Anyone know why there's a hard limit of 15 minutes for Lambda (and 9 minutes for Google Cloud Functions)? Still seems really weird to me.
Safety.
No function runs forever.
Also if you want to reboot/repurpose the server, 15 minutes is max wait time.
And finally, you don't want people running long jobs here when you have a solution there.
Re: AWS Lambda pricing now per ms
#14I've learned that AWS pricing tends to improve over time, and I appreciate it. I just recently switched from a startup offering authorization to AWS Cognito because the startup kept raising their price(s). It's nice to see this drop, though I'm sure Amazon does it due to competition as well.
It's nice to see that AWS is using their economy of scale to reduce their own costs, and passing that on to the consumer.
Re: AWS Lambda pricing now per ms
#15I am impressed that computation is billed by the ms nowadays. I'm an ignorant in AWS Lambda but how do you know if their ms measurement is accurate? Is there any way to verify this?
It's still measured by wall clock time - not CPU time. I'd love to see them bill for actual CPU time.
Re: AWS Lambda pricing now per ms
#16Anyone know why there's a hard limit of 15 minutes for Lambda (and 9 minutes for Google Cloud Functions)? Still seems really weird to me.
Lambda isn't designed for long running processes. Keeping the runtime limit lower makes it a lot easier to operate the underlying metal because you can move thing around every N minutes where N is the runtime limit. For long-running processes, something like Fargate might be a better fit in the AWS side of things.
Re: AWS Lambda pricing now per ms
#17Earlier quoted context omitted.
> So this is a pretty good advancement for cost savings. For some people. Those cost savings are made up somewhere else. Ultimately, Amazon is not a loss leader.
Why only for some people? It always rounded up to 100ms. If your function took 101ms, it was billed as 200ms.
If it takes 60 seconds, that's 600 steps. 601 steps isn't that much of a saving.
It matters close to 0.
Re: AWS Lambda pricing now per ms
#18I am curious to see if this will mean a shift to more efficient languages (Go or Rust) for Lambda services, as usually people default to JS
Re: AWS Lambda pricing now per ms
#19Anyone know why there's a hard limit of 15 minutes for Lambda (and 9 minutes for Google Cloud Functions)? Still seems really weird to me.
If I had to imagine designing a system like Lambda, people running really long operations would really throw a wrench in things.
Maybe you could let users indicate the operation will take a long time... but if the user knows the operation is long running in advance, why not just guide them to a more suitable system?
Re: AWS Lambda pricing now per ms
#20I am impressed that computation is billed by the ms nowadays. I'm an ignorant in AWS Lambda but how do you know if their ms measurement is accurate? Is there any way to verify this?
It's still measured by wall clock time - not CPU time. I'd love to see them bill for actual CPU time.
I'd bet a significant portion of their margins come from this, given Lambda's focus on I/O-bound workloads.