3 ms·

It is possible[1]. You are better off this way than the AWS "native" way. 1. https://dev.l1x.be/posts/2023/02/28/using-python-3.11-with-aws-lambda/ https://dev

It is possible[1]. You are better off this way than the AWS "native" way. 1. https://dev.l1x.be/posts/2023/02/28/using-python-3.11-with-aws-lambda/ https://dev.l1x.be/posts/2023/02/28/using-python-3.11-with-a...

easton 3y ago
The only problem with that is that Docker lambdas boot slower than lambdas with the built in runtime (not ridiculously slow, but could be 2x or something). God help you anyway if you’re trying to do something latency sensitive on Lambda, but if you are then you probably don’t want to add more time for a docker pull.
- Jochim 3y ago
  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...
  - re-thc 3y ago
    The situation does keep changing - AWS does optimize things. I'm not so sure it's a black/white true/false. Depends on what goes in the docker image. It's something like for larger deployments docker is faster but for small deployments it's the other way.
- squeaky-clean 3y ago
  We've actually observed the opposite at our company. Moving from a Python 3.8 built-in to Docker based changed our response times from about 40ms to 30ms on average.

3 ms·

It is possible[1]. You are better off this way than the AWS "native" way. 1. https://dev.l1x.be/posts/2023/02/28/using-python-3.11-with-aws-lambda/ https://dev

by datadeft 3y ago

easton 3y ago
The only problem with that is that Docker lambdas boot slower than lambdas with the built in runtime (not ridiculously slow, but could be 2x or something). God help you anyway if you’re trying to do something latency sensitive on Lambda, but if you are then you probably don’t want to add more time for a docker pull.
- Jochim 3y ago
  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...
  - re-thc 3y ago
    The situation does keep changing - AWS does optimize things. I'm not so sure it's a black/white true/false. Depends on what goes in the docker image. It's something like for larger deployments docker is faster but for small deployments it's the other way.
- squeaky-clean 3y ago
  We've actually observed the opposite at our company. Moving from a Python 3.8 built-in to Docker based changed our response times from about 40ms to 30ms on average.