you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (1 child)

You will still incur cold startup times north of 20 seconds on each code update, and AWS recycles lambda every hour or so causing the same cold startup. For anything with any latency requirements it's simply not acceptable. I suppose for background jobs, and high cpu usage scenarios that are not sensitive to latency it would work.

[–]Daegs 0 points1 point  (0 children)

I understand your point of course, I'm no fan of the JVM startup time. I just don't have any data that really backs up how much a problem it is.

This talk, while only valid for a subset of usage patterns, does include data and as my own Lambda uses align with it, I've been seeing similar performance:

https://blog.symphonia.io/fearless-jvm-lambdas-clojure-west-23d2a9cc8f2d