Should invokeCount not be invokeTotal?

[Jimmy89]

If you look at line 106 where is being checked whether a delay must be triggered within the lambda, the code looks at invokeCount, which increases for every invoke. I think this should be invokeCount >= invokeTotal, as otherwise only the first lambda that is called will be delayed, while all up following lambda triggers will have no delay (e.g. invokeTotal = 5, than invokeCount > 1 is true 4 times). In case invokeCount equals invokeTotal no delay is necessary.

Currently, this results into less lambda invokes that are warmed.

[naorpeled]

Hi,

Thanks for reaching out, and sorry for the delayed response.

Regarding line 106:

} else if (invokeCount > 1) {
  return delay(config.delay).then(() => true)
}

The condition invokeCount > 1 is intentional. The first invocation (invokeCount === 1) initiates the warming process without delay, while subsequent invocations (invokeCount > 1) introduce a delay to keep those Lambda instances warm.

Changing it to invokeCount >= invokeTotal would delay only the last invocation, leaving others unwarmed.

If Lambdas aren't being warmed as expected, it might be due to the default config.delay setting. Try increasing it to allow more time for warming.

Let me know if you have any questions.