Introduction

In the part 2 of our article series we explored how to develop and deploy pure Lambda function (without using any frameworks like Spring Boot 3) with Custom Runtime containing GraalVM Native Image with GraalVM 21 runtime and in the part 3 we measured the performance (cold and warm start times) of the Lambda function with 1024 MB of memory using this approach.

In this article we'll measure cold and warms starts of the Lambda with different memory settings between 256 and 1536 MBs to explore the tradeoff between cost and performance.

Measuring cold and warm starts of Lambda function with Custom Runtime containing GraalVM Native Image with different memory settings

We'll re-use exact the same experiment described in the part 3 of this article series but with different memory settings between 256 and 1536 MBs.

Here are results of the experiment:

Cold (c) and warm (m) start time in ms:

Conclusion

In this article measured cold and warms starts of the pure Lambda function having the memory setting between 256 and 1536 MB using Custom Runtime containing GraalVM Native Image with GraalVM 21 runtime.

We observe that warm start times are very close for each other also for setting lower memory like 256 or 512 MBs and difference is mainly visible for the high percentiles (>= p90). The cold start times are quite high for 256 and 512 MBs and starting from 768 MBs very decrease only a bit by giving Lambda more memory without any noticeable difference for memory greater than 1024 MB. Depending on your performance requirements you can give Lambda less memory than 1024 MBs as we initial gave in the sample application and have a very good price performance trade off with 768 MB or even a bit less memory.

At the time of publishing also newer versions became available (like GraalVM 23 runtime), so you case make the version changes and re-compile GraalVM Native image following the instructions from the part 2 of the series and re-measure the performance.