You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The AWS Lambda functions used in this application rely on tiered compilation.
After following the above blog, you should be able to create Lambda Layer and use AWS_LAMBDA_EXEC_WRAPPER as an environment variable for the 4 AWS Lambda functions.
Deployment
Deploy the demo to your AWS account using AWS SAM. Use serverless-groovy-demo as the app/stack name.
sam build && sam deploy --guided
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.
Load Test
Artillery is used to make 200 requests / second for 2 minutes to our API endpoints. You
can run this with the following command.
cd load-test
./run-load-test.sh
This is a demanding load test, to change the rate alter the arrivalRate value in load-test.yml.
CloudWatch Logs Insights
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