Hacker News new | ask | show | jobs
by philipkglass 1961 days ago
The article's "container lifespan" chart shows that 21% of containers live less than 10 seconds and 54% live <= 5 minutes. If the base data set has that many very-short-lived containers, it's probably not representative of containerized persistent services. How many services get CD updates every 10 seconds?

Indeed, the original Sysdig report that the chart comes from makes this case:

https://sysdig.com/blog/sysdig-2019-container-usage-report/

"Many containers need to only live long enough to execute a function and then terminate when it’s complete. Seconds may seem short, but for some processes, it’s all that is required. We believe the increased use of Kubernetes Jobs that run finite tasks like batch jobs contributed to this growth. In fact, we expect short lifespans to increase, especially on serverless platforms that are well-suited to running short term tasks."

1 comments

Good find. So sure, the lifespan is distributed down there, but surely there are some longer-lived services that benefit from JIT. I think most times you're spinning up a container + a JVM for what is effectively a function invocation you are maybe sad about paying the startup time for the JVM. Use Graal, or a different language?