I see this in the FAQ
I see this in the FAQ
Container cold starts can often be the 2-3 second range, but this is dependent on image size and code execution time, among other factors.Is this an estimate based on a certain size container?
3 Replies
This was just based on some internal testing. Though I will say this was a lot of relatively small golang and Node servers, so it does depend on whats happening on boot.
Is there a base container reference starting point for this (Dockerfile) ? because that is a pretty good cold start time ...
i have a use case for doing a static site build, that I would love to run in a container in line from a worker, i run it with bun usually because it is easier to run Typescript directly with Bun, and it it takes 1 to 3 seconds to run the process ... so only waiting a couple more seconds for a cold start is quite reasonable
Hey yeah so were using the hello-world example as the reference point.
Since then we shipped a change where we clamped down CPU for different instance types, and that ended up pushing the cold start times out more than we thought.
What we're going to do immediately is allow you to burst CPU usage beyond what your instance type "allows" at the start, so that your cold start time is good regardless of type.
Medium-term working on generalize cold start fixes**
Using snapshots
But I think we'll get back to the 2-3 second range at start of next week, and then push lower than that soon