There's this post: https://blog.thundra.io/solving-dotnet-lambda-cold-start-par...
It suggests a few things, including:
"one of the most intensive tasks at startup is jitting your machine agnostic .NET assemblies into machine specific"
It suggests a few things, including:
"one of the most intensive tasks at startup is jitting your machine agnostic .NET assemblies into machine specific"
That said, in everyday console apps on modern hardware the JIT is super quick at startup. I guess Lambdas are running in more constrained environments...