0

My team has a strange problem with our Lambda invocations, which seem to behave strangely from time to time. We are well aware of the cold start time and we addressed that with warmup Lambdas, but this is really strange.

Below I attached an image of the timeframe of a Lamba function invocation.

I takes 5-6 seconds for coldstart to happen, then the function runs for 700ms (billed period) and it again takes 5-6 second for response to happen. This happens a few time per hour, but it influences our apps badly becouse the app's rendering is impacted.

Anybody have a clue what is going on here?

enter image description here

John Rotenstein
  • 241,921
  • 22
  • 380
  • 470
Leon
  • 55
  • 6
  • 1
    How often are you running your warmup lambda to keep this specific lambda warm? If you aren't keeping it warm often enough then this could cause cold starts to still happen. – Chris Sep 18 '20 at 15:30
  • Every 5 mins. Cold start is taking only 1/3 of the time here. We don't have a clue what the other 2/3rds are? – Leon Sep 18 '20 at 15:47
  • 2
    Is this Lambda VPC attached? Do you have provisioned concurrency set up? – Shahad Ishraq Sep 18 '20 at 16:53
  • Yes it is VPC attached. Can you give me more info about provisioned concurrency, please? – Leon Sep 18 '20 at 19:10
  • @Leon https://docs.aws.amazon.com/lambda/latest/dg/configuration-concurrency.html – jellycsc Sep 18 '20 at 20:44
  • There seems to be a much deeper issue. No luck on the AWS forum also... https://forums.aws.amazon.com/thread.jspa?start=0&threadID=226136&tstart=0 – Leon Sep 19 '20 at 19:49

0 Answers0