I used to believe the same thing, I've began thinking it might now be false yet often repeated. AWS claims that: > Lambda also optimizes the image and caches

I used to believe the same thing, I've began thinking it might now be false yet often repeated. AWS claims that: > Lambda also optimizes the image and caches it close to where the functions runs so cold start times are the same as for .zip archives.[0] This[1] article shows almost no discernable difference in .NET cold start times between containerised and regular lambdas. It's easy to imagine developers pushing up bloated images, slowing startup down and blaming docker/AWS for it. [0] https://aws.amazon.com/blogs/compute/working-with-lambda-layers-and-extensions-in-container-images/ https://aws.amazon.com/blogs/compute/working-with-lambda-lay... [1] https://www.kloia.com/blog/aws-lambda-container-image-.net-benchmark https://www.kloia.com/blog/aws-lambda-container-image-.net-b...