Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Lambda pricing now per ms

aws.amazon.com

Post reply on HN
Print view View original

121–130 of 291 posts

Re: AWS Lambda pricing now per ms

#121

Post by tejohnso »

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…

> They also do not charge for bandwidth.

Is there fine print on this? Can I put 100TB / mo through their caching servers at the lowest $20 price tier?

Re: AWS Lambda pricing now per ms

#123

Post by throwaway894345 »

qvrjuec wrote: post #113
throwaway894345 wrote: post #75

Earlier quoted context omitted.

I haven’t heard that lambdas are “underpowered” before, but I’m interested to learn more. Could you elaborate just a bit on why they are underpowered?

Limitations on hardware one can run a lambda function on and constraints on execution time mean they are "underpowered" compared to other options, like ECS Fargate tasks.

Does Fargate allow you to run on beefier hardware? I know you can bring your own hardware with vanilla ECS. I’m aware of the execution time constraints (15 minutes), but I thought we were talking about 60s?

Re: AWS Lambda pricing now per ms

#124

Post by anonymoushn »

tejohnso wrote: post #121
ignoramous wrote: post #82

Earlier quoted context omitted.

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

> They also do not charge for bandwidth. Is there fine print on this? Can I put 100TB / mo through their caching servers at the lowest $20 price tier?

Yes, but you'll probably get an email about it.

Re: AWS Lambda pricing now per ms

#125

Post by [deleted] »

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

[deleted]

Re: AWS Lambda pricing now per ms

#126

Post by fitzoh »

throwaway894345 wrote: post #91
koolba wrote: post #59

Earlier quoted context omitted.

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

Wow, I haven’t read yet, but I’m very curious if this affects the size limits on the lambdas. I’ve tried to build lambdas for a small Python use case, but by the time I imported pandas and a few other libraries I exceeded the 250 mb limit and migrated to ECS/Fargate, but the startup times were much longer.

https://twitter.com/chrismunns/status/1333825503464214530

Docker containers can be up to 10gb, traditional lambdas are still limited to 250mb.

Re: AWS Lambda pricing now per ms

#127

Post by groundthrower »

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

Hi, are there any plans on offering instances with more CPU cores than the maximum 2 as I guess you have today?

Re: AWS Lambda pricing now per ms

#129

Post by munns »

groundthrower wrote: post #127
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

Hi, are there any plans on offering instances with more CPU cores than the maximum 2 as I guess you have today?

Yes, announced today you can go up to 10gb/6 vCPUs: https://aws.amazon.com/blogs/aws/new-for-aws-lambda-function...

Re: AWS Lambda pricing now per ms

#130

Post by thetrooper »

throwaway894345 wrote: post #91
koolba wrote: post #59

Earlier quoted context omitted.

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

Wow, I haven’t read yet, but I’m very curious if this affects the size limits on the lambdas. I’ve tried to build lambdas for a small Python use case, but by the time I imported pandas and a few other libraries I exceeded the 250 mb limit and migrated to ECS/Fargate, but the startup times were much longer.

yeah thats the issue. aws will make sure your fast language takes as much time as everything else - how will they make money if everyone makes use of fast languages?
Post reply on HN