Azure Features - Node vs. .Net Performance - ColdStart

Question

I do not know if this is done deliberately, or if Azure is poor in performance than AWS. Whenever I start working with Azure, it gets close to the minute.

The same cold action starts in less than a second (about 250 ms) with AWS.

As I see it, Azure stores all the function code in an Azure Storage account and downloads it over the network, creating this delay. This is with a consumption plan.

If I use the App Service Plan for functions, so junky even has this in modern applications. This can be reduced to 3 seconds, but even close to what AWS does.

How can I improve performance with Azure so that I can quickly launch my features?

Answer 1

I am a member of the Azure Functions team. I can assure you that we are not intentionally making JavaScript slow. This is simply due to some problems that we are still working with.

As you noted, the 60 second cold start performance you get is related to network latency that occurs when loading a very large number of small files, which is typical for node.js applications.

Our current recommendation is to use the Azure-Functions-Pack . It uses a web package to drastically reduce the number of files downloaded by your application.

, , Pack . , 2017 .