News for hackers. Stuff that matters.
Re:AWS Lambda Cold Start Times by laurencerowe on Tuesday October 12, 2021 @05:16PM (#28845189)
Couldn't this also have been handled efficiently in Lambda had it been configured to use batching? (Assuming it was implemented as async invocations driven by a queue of some sort.)

It does seem unfortunate that Lambda cannot be configured to support concurrent synchronous invocations for serving HTTP requests concurrently.

Re:AWS Lambda Cold Start Times by dralley on Tuesday October 12, 2021 @08:31PM (#28846817)
This is a bit like asking if you can make a coal-rolling pickup truck more environmentally friendly by letting your friends carpool with you.

Technically, yes, but it's kinda missing the point.

Re:AWS Lambda Cold Start Times by laurencerowe on Tuesday October 12, 2021 @11:06PM (#28847804)
I guess you're paying a 5x premium for Lambda in the constant usage scenario, a similar premium as on-demand vs spot instances.

4GB m6g.medium $0.0385/hour

4GB Lambda works out at $0.1920/hour

It's been a while since I last used queue driven autoscaling groups, but https://aws.amazon.com/blogs/compute/scaling-your-applicatio... has startup time of about 4 minutes from scratch or 36s from a paused instance in a 'warm pool.' vs less than a second for Lambda in the original article. So the decision ends up coming down to responsiveness vs cost. Presumably Fargate comes somewhere in between.