CODEWITHSUNDEEP
.netnode.jsazure-functionsazure-functions-runtimecold-start
mattipet
mattipet

Reputation: 377

Azure Functions language and runtime version choice to minimize cold-start time

I'm starting a new project that has strict requirements that the cold-start time has to be minimal. We are talking about sub-second response-time. I haven't found any comparison of the cold-start times by language and runtime version.

Does anyone know of a benchmark of for example is C# cold-start time faster that Node.js or vice versa? What about runtime v1 vs v2?

In here: https://blogs.msdn.microsoft.com/appserviceteam/2018/02/07/understanding-serverless-cold-start/ it says that

Also, it’s important to note that any language running in our 2.0 runtime is in preview and also hasn’t been optimized fully.

but what does that actually mean? How much faster is v1? Is this likely to change in the future to the benefit of v2?

Upvotes: 3

Views: 899

Answers (1)

Mikhail Shilkov
Mikhail Shilkov

Reputation: 35134

As of today (april 2018), for a "Hello World" function cold start will be

  • Very similar for Javascript and for precompiled .NET
  • Much less for V1 than for V2

Typical cold startup time for V1 Javascript and precompiled .NET is between 1.5 and 4 seconds.

You can read the detailed analysis in Azure Functions: Cold Starts in Numbers.

Upvotes: 4

Related Questions