Introduction

In the Part 12 of our series we measured the cold starts of the Lambda function with Corretto Java 21 runtime without SnapStart enabled, with SnapStart enabled and also applied DynamoDB invocation priming optimization with different Lambda function memory settings . In this article we’d like to do the same measurement but for Corretto Java 17 runtime and then do comparison between both.

Measuring cold starts with Java 17 with and without SnapStart enabled using different Lambda memory settings

In our experiment we'll re-use the application introduced in part 8 for this. Here is the code for the sample application. There are basically 2 Lambda functions which both respond to the API Gateway requests and retrieve product by id received from the Api Gateway from DynamoDB. One Lambda function GetProductByIdWithPureJava17Lambda can be used with and without SnapStart and the second one GetProductByIdWithPureJava17LambdaAndPriming uses SnapStart and DynamoDB request invocation priming. We'll measure cold starts using the following memory settings in MBs : 256, 512, 768, 1024, 1536 and 2048.

The results of the experiment below were based on reproducing approximately 100 cold starts for the duration of our experiment which ran for approximately 1 hour. For it (and all experiments from my previous articles) I used the load test tool hey, but you can use whatever tool you want, like Serverless-artillery or Postman

Cold start time without SnapStart in ms:

Cold start time with SnapStart without Priming in ms :

Cold start time with SnapStart enabled and with DynamoDB invocation Priming in ms :

I also measured the deployment time of such sample project with all memory settings mentioned above with SnapStart enabled for all functions and GetProductByIdWithPureJava17LambdaAndPriming function additionally using priming. Here are the results:

Conclusions

In this article we measured the cold start time of the Lambda function without SnapStart with SnapStart and for the latter with additional priming of DynamoDB invocation for Java 17 runtime.

In case of not enabling SnapStart we observed that increasing the memory from 256 MB to 2048 MB constantly brought significant reduction of the cold start time. We observed the same with Java 21 runtime, but cold start times with Java 17 runtime being a bit lower than with Java 21 runtime (for the relative early version of Java 21 used for the measurements)

In case of enabling SnapStart but not using priming we observed that increasing the from 256 MB to 1536 MB brought significant reduction of the cold start time with very low impact of increasing the memory from 1536 MB or even to 2048 MB. We observed similar with Java 21 runtime, but the impact of increasing memory even beyond 1024 MB already became lower. The cold start times with Java 17 runtime were also a bit lower than with Java 21 runtime (for the relative early version of Java 21 used for the measurements)

In case of enabling SnapStart and with additional priming of DynamoDB invocation we observed that increasing the from 256 MB to 1024 MB brought significant reduction of the cold start time but after that the impact of increasing the memory to 1536 MB or 2048 MB was low or even negative for all percentiles. We observed the same with Java 21 runtime. Also the result of using Java 17 and Java 21 runtimes are very close.

So for the SnapStart-enabled Lambda function and considering our use case with Lambda function reading from the DynamoDB table the Lambda memory setting of 1024 MB is a good choice.

Deployment time for the SnapStart enabled on all 3 Lambda functions and additionally applying priming on one of them also became lower by giving the Lambda function more memory but only until 786 MB. After that we even observed the small increase of the deployment time. With Java 21 runtime we observed decrease of the deployment time by giving the Lambda function more memory until 1024 MB and then relative stable deployment time by giving Lambda function even more memory.