The article discusses optimization strategies for cold and warm starts in Quarkus 3 applications on AWS Lambda.
Previous articles in the series covered running and optimizing Quarkus 3 applications on AWS Lambda with managed Java 21 runtime and GraalVM Native Image.
Performance measurements included Lambda functions using 1024 MB memory, specific Java compilation options, x86_64 architecture, and default Apache HTTP Client.
Optimization techniques for additional Lambda performance improvements are introduced in this article.
Suggestions include trying different memory settings, using Lambda arm64 architecture, and exploring various synchronous and asynchronous HTTP clients.
Different Java compilation options and excluding unused dependencies can also impact cold and warm start times.
The article emphasizes the importance of measuring performance improvements and potential optimization strategies for Quarkus 3 applications on AWS Lambda.