Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Comments to "Reducing Cold Start Duration in Azure Functions" #7
Thanks for this article. I must confess I'm still slightly confused by the various deployment options and which you are talking about .
When I previously used JS Function's on Windows (before Linux option) I found the node-modules folder had to be bundled to get a sensible cold start (there's a Microsoft repo for this somewhere).
I recently asked if this still applied or is perhaps different on Linux hosted functions as the slow Windows share seemed to be the problem - MicrosoftDocs/azure-docs#27181 The answer suggested I should use the package deployment which appears to be different to the old zip method in Kudu and is perhaps the same as you mention as zip - or might be different. Can you shed any light? Thanks
Basically, Local Zip and External Zip are "Run from Package" deployment as described here. I believe that's what you got recommended. As I mentioned, in theory, it should have reduced the cold start, but it hasn't.
All my Node.js tests are on Windows. I actually believe you can't get Node.js Consumption on Linux as of today.
@mikhailshilkov Thanks for clarifying and it's good to hear there aren't even more options. I guess your 'local' is
Re Lunix, I'm sure I read an announcement of GA but now can't find it. However, this docs article specificaly mentions JS on Linux (which is only via nodejs AFAIK). I would assume available on consumption as that is the entire point of Functions. But to be honest, I don't care if Windows or Linux hosted, unless have native modules or bash npm scripts (which are a pain on Windows npm as it assumes cmd).
Update: Ah, Linux on consumption plan is a limited preview right now.