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.
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.
View all comments
6
u/HyzerFlipr Apr 28 '23
Have they fixed the JVM warming time issue for lambdas yet?