Cold Starts in Azure Functions
This article describes Azure Functions running on Consumption Plan—the dynamically scaled and billed-per-execution compute service. Consumption Plan adds and removes instances dynamically. When a new instance handles its first request, the response time increases, which is called a cold start.
Learn more: Cold Starts in Serverless Functions.
When Does Cold Start Happen?
The very first cold start happens when the first request comes in after deployment.
After that request is processed, the instance stays alive for about 20 minutes to be reused for subsequent requests:
How Slow Are Cold Starts?
The following chart shows the typical range of cold starts in Azure Functions V2, broken down per language. The darker ranges are the most common 67% of durations, and lighter ranges include 95%.
View detailed distributions: Cold Start Duration per Language.
Is V2 Faster Than V1?
There are currently two generally available versions of Azure Functions runtime: V1 runs on top of .NET Framework 4.x, while V2 runs on .NET Core 2.x.
Even though .NET Core is supposed to be faster and more lightweight, Functions V2 still experience longer cold starts:
Does Package Size Matter?
The above charts show the statistics for tiny “Hello World”-style functions. Adding dependencies and thus increasing the deployed package size will further increase the cold start durations.
Indeed, the functions with many dependencies can be several times slower to start.