Just in case you've never tried an AWS Lambda function written in GoLang, you absolutely should: https://aws.amazon.com/blogs/compute/announcing-go-support-for-aws-lambda/ … It's fast. I mean really fast.
-
-
It wasn't faster for cold boots. In fact, Node 0.10 was the fastest in my testing – because the min binary size in Go is around 8MB vs a few bytes in Node – but tbh it's a bit of a wash. The Go runtime cheats with its reporting, amortizes startup (good for consumers!)
-
There may have been some AWS Lambda changes since you did that. Node 0.10 was a while ago.
-
Should have clarified – this was using the Node.js 0.10 binary on a Go runtime Lambda. The Node script starts a socket server and speaks Gob to the Lambda controller.
-
A Rust binary was even faster actually (because it was 474kb vs 8MB for Go). Bit of discussion about cold start time here:https://twitter.com/hichaelmart/status/953499155011461121 …
-
I'm really only talking about the supported Go in Lambda rather than anything else. A warm Go Lambda function can run in less than 1ms (YMMV depending on function of course)
-
Sure, but
@JoeEmison was asking about startup time (which I assume means cold start time). Warm is fast, for sure
-
There's some more comparisons here: https://twitter.com/fsenart/status/962070727330377735 … – 95th percentile isn't that different. Problem is they don't account for time outside the "container" – ie, mounting /var/task – where Go's 8MB minimum hurts it. Need to measure from the API really.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.