0x161e-swei commented on PR #176: URL: https://github.com/apache/openwhisk-runtime-go/pull/176#issuecomment-1255271832
> @0x161e-swei BTW, why do you enable this configuration for the go runtime that does not support concurrency? Hi @style95, there seems to be no way to enable concurrency for a specific runtime, the `action.limits.concurrency.maxConcurrent` configs are used inside ContinaerProxy and Invoker. I had it enabled sicne I was playing with nodejs runtime as well. > I am curious if such mixed results could happen without concurrency enabled as well. According to [this line](https://github.com/apache/openwhisk/blob/master/core/invoker/src/main/scala/org/apache/openwhisk/core/containerpool/ContainerProxy.scala#L428): Without the concurrency enabled (max set to 1), the ContainerProxy won't send another request until the first one completed and returned. > I am not sure if there are problems also in the initialization but AFAIK each runtime can be initialized only once! Hi @msciabarra, with a single executor and runtime, we will not be initializing the runtime twice since the action proxy will only be writing to the stdin of the underlying action process. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
