travigd commented on pull request #4978: URL: https://github.com/apache/openwhisk/pull/4978#issuecomment-693722522
> Separately, there will probably need to be additional special handling for concurrent actions I'm thinking the best way to handle this would be a queue-per-action, and then when a new activation is received, check against the total number of containers that could handle that action. I think that still has issues around fairness though. When do you shutdown a container to schedule a new action container? The "naive" implementation would just keep containers around as long as there are activations to process, even if there's an action that can't be scheduled that's been waiting for much longer. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
