...and the language choice has a measurable impact on the cold start time. I've measured it - as have others[1][2].
You're right that it's not just about the language runtime though. I must admit I'd forgotten about the container spin up et al as well (thankfully the recent ENI fix for VPC lambda's has been released because that was threatening to bite us hard on one project).
That first link makes no sense. The C# is not reflective us my real-world usage in the slightest bit. The 2nd link is more accurate to my experience, and obviously contradicts the first link.
I haven't tested the new VPC stuff yet to know what the impact is.
> That first link makes no sense. The C# is not reflective us my real-world usage in the slightest bit. The 2nd link is more accurate to my experience, and obviously contradicts the first link.
They don't contradict each other. They're different graphs demonstrating different workloads. You'd be surprised just how much peoples "real-world usage" can vary from one customer to another.
> I haven't tested the new VPC stuff yet to know what the impact is
Pretty significant for high demand lambda's. Unfortunately I'm not sure how much of what I know is covered by NDA so apologies for not being more specific.
Ok, so I commented on the authors blog post and he linked me to the repo, I took his code and compiled it myself and was unable to reproduce the result he got, he also said:
> Yes, I'm also suspicious about my C# results at this point.
I'm not sure how he got the results he got. So it maybe worth him running the test again.
You're right that it's not just about the language runtime though. I must admit I'd forgotten about the container spin up et al as well (thankfully the recent ENI fix for VPC lambda's has been released because that was threatening to bite us hard on one project).
[1] https://mikhail.io/serverless/coldstarts/aws/languages/
[2] https://levelup.gitconnected.com/aws-lambda-cold-start-langu...