5 ms·
Container launch times are frequently in minutes if we include pulling the images from a repo, which we reasonably should. In whichever case, that doesn't mean
by throwaway894345 6y ago
Container launch times are frequently in minutes if we include pulling the images from a repo, which we reasonably should.
In whichever case, that doesn't mean we can't compose them into a performant product as the OP suggests, it just means you run them as daemons so you can amortize the startup cost across many invocations. This isn't specific to containers--we do the same thing for web servers, databases, virtual machines, physical machines etc. Anything with a startup cost that you don't want to pay each time.
- pm90 6y agoWhy would you include pulling the container image as something that should be a part of the container launch time? It’s a one time event after a code push.
- mrkurt 6y agoIt's not a one time event, each host that runs a container image needs to pull it at least once. Minimizing pulls is a good optimization but you have to work pretty hard to really cut them down.