Deploy the demo to your AWS account using AWS SAM.

mvn clean package
sam deploy -g

SAM will create an output of the API Gateway endpoint URL for future use in our load tests. Make sure the app name used here matches with the STACK_NAME present under load-test/run-load-test.sh

mvn clean package -Pnative
sam deploy -t template.native.yaml -g

SAM will create an output of the API Gateway endpoint URL for future use in our load tests. Make sure the app name used here matches with the STACK_NAME present under load-test/run-load-test-native.sh

Artillery is used to make 100 requests / second for 10 minutes to our API endpoints. You can run this with the following command under load-test directory:

cd load-test

Before running load tests, make sure you update the stack name in load test bash script

./run-load-test.sh

Before running load tests, make sure you update the stack name in load test bash script

./run-load-test-native.sh

This is a demanding load test, to change the rate alter the arrivalRate value in load-test.yml.

Using this CloudWatch Logs Insights query you can analyse the latency of the requests made to the Lambda functions.

The query separates cold starts from other requests and then gives you p50, p90 and p99 percentiles.

filter @type="REPORT"
| fields greatest(@initDuration, 0) + @duration as duration, ispresent(@initDuration) as coldStart
| stats count(*) as count, pct(duration, 50) as p50, pct(duration, 90) as p90, pct(duration, 99) as p99, max(duration) as max by coldStart

Latency for JVM version:

Latency for GraalVM version:

You can add additional detail to your X-Ray tracing by adding a TracingInterceptor to your AWS SDK clients.

Example cold start trace for JVM version:

Example cold start trace for GraalVM version:

Example warm start trace for JVM version:

Example warm start trace for GraalVM version: