3 ms·

Since you're using Firecracker, it's hard to understand how it takes 20 seconds to boot a VM. AWS Lambda worst performer (JVM) I think takes much less than tha

Since you're using Firecracker, it's hard to understand how it takes 20 seconds to boot a VM. AWS Lambda worst performer (JVM) I think takes much less than that, like 5 seconds in cold start. You must be loading something really bulky at startup... Why don't you offer warmed VMs? Like reserved concurrency in AWS Lambda. Preemptively increase the number of VMs (like an auto-scaler) as traffic increases.

mlejva 5y ago
I understand from where your confusion comes from. We have a few unoptimized things happening on our infra in the moment. We are working on it to make it better and it will be better soon. Most likely around 1-2 seconds. Once we had the early version ready, we started focusing on figuring out the business side of Devbook and iterating on the product. So certain things aren't as high priority right now but will be very high in the near future.