I've got an API Gateway V2 (Protocol:HTTP) style endpoint, it simply makes a request to my Lambda function and gives me the response. I've noticed that if I make no request for about 10 minutes or so, that on a new request it's going WAY slower than the requests afterwards. It's the same function that does the same thing every time so I'm not sure why this is happening, has anyone else ever had this and found a solution?

CodePudding user response：

The reason for this is that your Lambda function has to be started before it can handle requests.

This is also called cold start.

Starting a new instance of your Lambda does take some time. Once it is started it will serve several requests. At some point in time the AWS Lambda service is going to shutdown your Lambda function. For example when there has not been any traffic for a while.

That's where your observation is coming from:

I've noticed that if I make no request for about 10 minutes or so, that on a new request it's going WAY slower than the requests afterwards.

When there are no instances of your Lambda running and a new requests is coming in, the AWS Lambda service needs to instantiate a "fresh" instance of your Lambda.

You could read this blog which touches this topic:

https://aws.amazon.com/blogs/compute/operating-lambda-performance-optimization-part-1/