- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
I think it is exactly what you say. During cold start you get a boost of CPU. I think you do not get the boost during Provisioned Concurrency initialization.
You can prove this by increasing your function's memory to 1.7GB. In this case you will get approximately the same amount of CPU as the boost you get.
Hi, If you look at the diagrams of https://aws.amazon.com/blogs/compute/operating-lambda-performance-optimization-part-1/, you will notice that the so-called "Execution Initialization Code" in the post happens as part of lambda execution itself in a cold start while it happens as part of initialization phase with provisioned concurrency. (see the blue squares)
That's 1 reason why its longer wit provisioned concurrency.
Best,
Didier
I see what you mean but that would impact only overal 'cold start' metric (because now it runs some extra code). But on top of that I see that the 'Initialization Code' executes 4 times faster when it runs as part of lambda execution itself and is very slow when it runs as part of initialization phase with provisioned concurrency.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Thank you for confirming. Tested and with more CPU On-Demand instances are still a bit faster but the difference is not that visible (10-20%)