Hi, that should still be possible without needing excessive container recreates. Do you see anything blocking your use-case?
Am 06. September 2017 um 08:17 schrieb mandeep gandhi <[email protected]>: Hi Markus, Actually, I am trying to orchestrate a workflow via open-whisk which would involve a request payload passing through a sequence of actions. So I have a mixed bag of heterogeneous micro services I want to mimic as actions. I had already gone through your blog earlier. On Wed, Sep 6, 2017 at 11:27 AM, Markus Thömmes <[email protected]> wrote: Hi Mandeep, OpenWhisk relies on container reuse (i.e. using warm containers) heavily to reach its performance goals. Currently, containers are kept around for a maximum of 10 minutes if they are not replaced by the need of some other container. You can refer to this article written by me (shameless self-advertisement) to get some insights into how our container caching works: https://medium.com/openwhisk/squeezing-the-milliseconds-how-to-make- serverless-platforms-blazing-fast-aea0e9951bd0 You can refer to the relevant source code here: - https://github.com/apache/incubator-openwhisk/blob/ master/core/invoker/src/main/scala/whisk/core/ containerpool/ContainerProxy.scala - https://github.com/apache/incubator-openwhisk/blob/ master/core/invoker/src/main/scala/whisk/core/containerpool/ContainerPool. scala Anything more you can think of for your use-case? Cheers, Markus Am 06. September 2017 um 07:50 schrieb mandeep gandhi < [email protected]>: Hi, I was looking for the support of warm containers for JVM and Python based containers. I have a use case where I want to run some scala/java micro services and some TensorFlow containers for my workflow. Now as these containers would take some seconds to get up, I would like to know - a. What is the current status for the same? b. How can we contribute to it if the support is missing? Thanks, Mandeep Gandhi
