AWS Lambda pricing now per ms • Hacker News Board

Re: AWS Lambda pricing now per ms

#81

Post by SamBam » Tue, Dec 01, 2020, 6:19 PM UTC

AndersSandvik wrote: post #24

66$ for running a AWS Lambda with 128 for a year seems very expensive.

If you're running at 100% of the time, don't use a Lambda. If you're running for 10 seconds a day, a Lambda is cheaper than owning your own hardware.

Similarly, if a car rental costs $20/day, it would be silly to say that that's expensive because it will cost you $73,000 after 10 years. The needs of a car rental and car ownership are different.

Re: AWS Lambda pricing now per ms

#82

Post by ignoramous » Tue, Dec 01, 2020, 6:19 PM UTC

munns wrote: post #56

catchmeifyoucan wrote: post #2

For reference - Lambda functions used to billed at 100ms intervals. My Node.Js function usually only takes 37-40ms to run. So this is a pretty good advancement for cost savings.

Awesome! That was the idea here. Lots of sub 100ms workloads and we really want you to be able to pay for what you use. - Chris, Serverless@AWS

> ...we really want you to be able to pay for what you use.

Cloudflare Workers has the right pricing model. They only charge for CPU time and not wall time. They also do not charge for bandwidth.

> Lots of sub 100ms workloads...

AWS Lambda (or Lambda at Edge), as it stands, is 10x more expensive for sub 50ms workloads (Workers does allow upto 100ms for the 99.9th percentile) that can fit 128MB RAM.

https://medium.com/@zackbloom/serverless-pricing-and-costs-a...

Re: AWS Lambda pricing now per ms

#83

Post by colechristensen » Tue, Dec 01, 2020, 6:19 PM UTC

SamBam wrote: post #78

dezmou wrote: post #73

There will be more surprise in bills, imagine if your Lambda is making a call to an API and this API suddenly slow down for any reason

How does this change increase the likelihood of that happening?

Before the 100x courser granularity would hide a lot more variation if your lambdas were quick.

Re: AWS Lambda pricing now per ms

#84

Post by jusssi » Tue, Dec 01, 2020, 6:19 PM UTC

munns wrote: post #49

yeldarb wrote: post #3

Anyone 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.

How long would you like it to be? Chris Munns - Lead of Dev Advocacy for Serverless@AWS

Now that someone's listening: I don't mind the 15min Lambda timeout, but it would be great to get rid of the Lambda + API Gateway 30s & ~6MB limits. Those always bite unaware devs in the butt and workarounds for them take quite a bit of effort.

Re: AWS Lambda pricing now per ms

#85

Post by bdcravens » Tue, Dec 01, 2020, 6:19 PM UTC

koolba wrote: post #59

jlouis wrote: post #6

Necessary change. Now writing stuff in fast languages suddenly matter in cost, changing the landscape of when these solutions might become viable for a chase.

And you can pick any language you'd like as it supports arbitrary containers now too: https://news.ycombinator.com/item?id=25267182

For per ms billing to matter, you probably want to limit your language choices.

Re: AWS Lambda pricing now per ms

#86

Post by simlevesque » Tue, Dec 01, 2020, 6:21 PM UTC

This means that using bigger CPUs (by allocating more RAM) just became even more important.

Re: AWS Lambda pricing now per ms

#87

Post by narag » Tue, Dec 01, 2020, 6:23 PM UTC

jlouis wrote: post #6

Necessary change. Now writing stuff in fast languages suddenly matter in cost, changing the landscape of when these solutions might become viable for a chase.

I've been here for a while resisting the temptation to write a sarcastic comment. Speed has been the opposite of what matters for decades. Every change is always trading speed for something else. And suddenly some offer by Amazon is going to change that? Seems unlikely.

Re: AWS Lambda pricing now per ms

#88

Post by vikramkr » Tue, Dec 01, 2020, 6:23 PM UTC

Supermancho wrote: post #7

catchmeifyoucan wrote: post #2

For reference - Lambda functions used to billed at 100ms intervals. My Node.Js function usually only takes 37-40ms to run. So this is a pretty good advancement for cost savings.

> 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.

This is also a competitive market. Aws has to fight against gcp and azure for new customers, and in a competitive market, you don't get a guarantee to make up the money you lose somewhere else.

Re: AWS Lambda pricing now per ms

#89

Post by munns » Tue, Dec 01, 2020, 6:23 PM UTC

ignoramous wrote: post #82

munns wrote: post #56

Earlier quoted context omitted.

Awesome! That was the idea here. Lots of sub 100ms workloads and we really want you to be able to pay for what you use. - Chris, Serverless@AWS

> ...we really want you to be able to pay for what you use. Cloudflare Workers has the right pricing model. They only charge for CPU time and not wall time. They also do not charge for bandwidth. > Lots of sub 100ms workloads... AWS Lambda (or Lambda at Edge), as it stands, is 10x more expensive for sub 50ms workloads (Workers does allow upto 100ms for the 99.9th percentile) that can fit 128MB RAM. https://medium.com…

Except that none of the rest of your infrastructure is there, and that APIs represent just a non-majority part of Lambda workloads.

Re: AWS Lambda pricing now per ms

#90

Post by colechristensen » Tue, Dec 01, 2020, 6:25 PM UTC

AndersSandvik wrote: post #24

66$ for running a AWS Lambda with 128 for a year seems very expensive.

Yes, and buying a server, powering/cooling it, and maintaining it for a three or five year lifetime to be utilized 5% is also expensive.

Lots of choices are expensive, pick the one that’s best for your use case.