1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
this issue is a known one: https://github.com/aws/aws-lambda-base-images/issues/83
It seems to have been recently resolved:
While everyone is pinged, it's good to note that cold starts in node.js 18
AWS-managed runtimes have been greatly reduced.
For node.js 18, you can see archive.org on Feb 1, 2023, cold starts were: 219.719ms
And today, May 30, 2023: 173.99ms.
That's more than 20% decrease, which is huge, thank you @jtuliani and the rest of AWS.
==========
Thank you for noticing @o-alexandrov :)
Yes, we have deployed updates to the AWS Lambda Node.js18 runtime which bring
the cold start times close to the performance with Node.js 16. We are continuing
to investigate further optimizations. To reduce the risk of backward compatibility issues,
any further optimizations will be focused on Node 20 rather than being back-ported to
existing runtimes.
Therefore, closing this item.
Best,
Didier
Relevant content
- asked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 5 months ago
I saw that issue and it does not match my observations from the beginning of August. Maybe "cold start times close to the performance with Node.js 16" means more of a difference than I would think?