You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by gi...@git.apache.org on 2017/09/22 06:41:49 UTC

[GitHub] markusthoemmes commented on issue #2795: enable concurrent activation processing

markusthoemmes commented on issue #2795: enable concurrent activation processing
URL: https://github.com/apache/incubator-openwhisk/pull/2795#issuecomment-331363975
 
 
   Read briefly over the code, good for a start ? 
   
   The changes in ContainerProxy look good to me on first glance. I wonder if  we can simplify on the scheduling bits though: What if we tracked the number of concurrent invocation always and only update to Busy, if that number reaches `max`. Everything else will put the container into `Free`.
   
   In the non-concurrent case that number can be set to 1. I think we could get away without any changes to the scheduler in that case, since the ContainerPool itself keeps the state-tracking consistent. WDYT?
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services