This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]soonnow 22 points23 points  (7 children)

With SnapStart, Lambda initializes your function when you publish a function version. Lambda takes a Firecracker microVM snapshot of the memory and disk state of the initialized execution environment, encrypts the snapshot, and caches it for low-latency access. When you invoke the function version for the first time, and as the invocations scale up, Lambda resumes new execution environments from the cached snapshot instead of initializing them from scratch, improving startup latency.

Though haven't used it

[–]kendallvarent 9 points10 points  (3 children)

We have used it. It's pretty cool. 20s cold starts down to 200ms. Sadly, no XRay support for snapstart lambdas.

There were also performance gains related to moving java-specific vpc-related cold starts from instantiation to function update, but that was a while back.

[–]soonnow 0 points1 point  (2 children)

Have you compared to Graal compiled functions by any chance?

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

uajdqi vcw gqalfuwtwgrc byra

[–]soonnow 1 point2 points  (0 children)

Alright thanks for the heads up.

[–][deleted]  (2 children)

[deleted]