JAR size affect the response time of lambda?
I'm making some experiments regarding the impact of JAR size on Lambda Cold Starts and response times. I have created 3 JARs of different sizes.
|JAR Size||Response time|
In Cludwatch logs I can see that init durations for all these Lambas is on average ~620ms, but for every lambda the response time is different and I don't know why. The code is the same(there is no logic -> all of them are returning a String), differences in size are due to different maven dependencies that I added. All of them are from AWS SDK. Is this normal?
Yes. the size of function package can affect the cold start time. You can refer this blog (https://aws.amazon.com/ko/blogs/compute/operating-lambda-performance-optimization-part-2/)
Lambda Authorizer Context Response Size LimitAccepted Answerasked 3 months ago
lambda cold start & synchronous executionAccepted Answerasked 4 years ago
How long does a lambda instance can keep 'warm'?asked 5 months ago
Recommended Lambda function sizeAccepted Answerasked 3 years ago
How to increase index.max_result_window on Elasticsearch?asked a month ago
AWS Lambda - Body Size is Too Large Error, but Body Size is Under Limitasked a year ago
lambda take few seconds to return responseasked a month ago
Lambda using docker - Billed time very high for small durationAccepted Answerasked 8 days ago
JAR size affect the response time of lambda?asked a month ago
What is the maximum size for a lambda docker image ?Accepted Answerasked a year ago