AWS Lambda pricing now per ms

Re:AWS Lambda pricing now per ms by groundthrower on Tuesday December 01, 2020 @01:52PM (#25268436)

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

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by munns on Tuesday December 01, 2020 @01:53PM (#25268452)

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

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by groundthrower on Tuesday December 01, 2020 @02:00PM (#25268534)

Okay, nice. And if I would like like 32 vCpus? Having an application today that has a huge degree of parallelism, but utilizing an external cloud provider that offers dedicated machines with very affordable pricing. Would really like to use lambdas instead though.

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by munns on Tuesday December 01, 2020 @02:06PM (#25268596)

Interesting. Not possible today. We'd still encourage paralyzation up through multiple concurrency of functions being executed.

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by JoshTriplett on Tuesday December 01, 2020 @02:46PM (#25269029)

I would love to see this as well: having 96-vCPU Lambda instances (or instances that match the biggest C-family instance you have) would solve a lot of problems for me. The execution model of Lambda (start a runtime, handle requests, AWS handles pool management) feels much easier to use than managing a pool.

Someone from AWS once commented to me that "if you're ever having to manage a pool rather than letting us manage it, that's a gap in our services".

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by chrisweekly on Tuesday December 01, 2020 @10:59PM (#25273106)

"paralyzation" -> parallelization, yeah? :)

[ Parent | on HN ]

Re:AWS Lambda pricing now per ms by munns on Wednesday December 02, 2020 @11:04AM (#25277631)

It was a long day yesterday, thank you :)

[ Parent | on HN ]