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

91–100 of 291 posts

Re: AWS Lambda pricing now per ms

#91

Post by throwaway894345 »

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

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.

Re: AWS Lambda pricing now per ms

#92

Post by tanilama »

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.

To limit the scope, and type of applications people should use Lambda for and Lambda is best at running them.

15 mins max runtime simplifies the resource management and avoid abuse. If you have workload for long running jobs, then that should go to something like AWS EKS/Batch/SageMaker.

That being said, things can change, if more and more people requires long running capacity for Lambda (though I am skeptical of that, as Lambda abstracts the underlying hardware away and is supposedly flexible to the requirements)

Re: AWS Lambda pricing now per ms

#93

Post by Dunedan »

Scarbutt wrote: post #70
camhart wrote: post #5

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

I just recently switched from a startup offering authorization to AWS Cognito because the startup kept raising their price(s). Maybe because they know Cognito is horrible? ;) OTOH, I have never seen DynamoDB prices decreasing.

The introduction of DynamoDB on-demand pricing was a huge price reduction for some workloads with the additional benefit of also reducing the complexity of scaling capacity as well.

Re: AWS Lambda pricing now per ms

#94

Post by munns »

jusssi wrote: post #84
munns wrote: post #49

Earlier quoted context omitted.

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.

Yes.

But being real, we hear you on this one. I can't comment on API Gateway's roadmap here but this is something both teams is aware of. The reason it is the way it is today is for a valid reason. But this is def something we hear pretty often.

- Chris

Re: AWS Lambda pricing now per ms

#96

Post by mrits »

munns wrote: post #89
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…

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

To be clear, you're acknowledging Cloudflare has a much better pricing model but just not as many other services yet?

Re: AWS Lambda pricing now per ms

#97

Post by throwaway894345 »

valbaca wrote: post #48
brunoluiz wrote: post #18

I 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

From the research I did, here's how languages stack up in Lambda runtime (lowest first): 1. Python & JS 2. Go 3. C# & Java I couldn't find any data on Rust. The understanding at the time was that Python & JS runtimes are built-in, so the interpreter is "already running" Go is the fastest of compiled languages, but just can't beat the built-in runtimes. C# and Java were poorest as they're spinning up a larger runtime…

I’m not sure I’m interested in a hello world benchmark if it takes Python 5 seconds to import its dependencies in the real world.

Re: AWS Lambda pricing now per ms

#98

Post by londons_explore »

jeffbee wrote: post #52
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.

Just out of curiosity, what are you getting out of your 160 million CPU cycles? Are you mostly on the CPU, or mostly waiting for something (database call or whatever)?

I want to do something that a low level hacker could do in 100 clock cycles with hardcoded bit twiddling and some avx-512, but I want to use nodejs, so I'm gonna need at least 100 million clock cycles to parse all the npm modules...

Re: AWS Lambda pricing now per ms

#99

Post by alexeldeib »

donor20 wrote: post #38
astuyvenberg wrote: post #15

Earlier quoted context omitted.

It's still measured by wall clock time - not CPU time. I'd love to see them bill for actual CPU time.

They would be willing to do this probably if you let them evict your entire workload from memory during the period you were not paying for it, and then were able to charge you for CPU time and some additional charge to reload workload into memory from hibernation. Most workloads ALSO hold memory (which is a key constraint) over the entire wall clock time, and the delays and impacts/costs of hibernating out the memory…

They could also charge you some rate for CPU seconds + Gb-seconds of memory used? Sort of the ultimately flexible cloud platform. You could apply the same sort of thinking to other resources, but it works best for CPU/memory I think.

Re: AWS Lambda pricing now per ms

#100

Post by jacobra2 »

Scarbutt wrote: post #70
camhart wrote: post #5

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

I just recently switched from a startup offering authorization to AWS Cognito because the startup kept raising their price(s). Maybe because they know Cognito is horrible? ;) OTOH, I have never seen DynamoDB prices decreasing.

What don't you like about cognito? I've been able to solve every auth problem I've encountered with it.
Post reply on HN