It has always had much slower cold start times than other choices:
Ways for better c# production startup (AWS or on Prem) * Compile in Release mode * Test Ahead-Of-Time (AOT) mode * Limit code size. The JIT reading 200mb+ of code will be slow compared to a 15mb deployment.
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...