[GitHub] [openwhisk] BillZong opened a new issue #4650: CPU limit mode scheduling feature that might needed

[GitBox <gi...@apache.org>]

BillZong opened a new issue #4650: CPU limit mode scheduling feature that might needed
URL: https://github.com/apache/openwhisk/issues/4650
 
 
   Currently, the container scheduling strategy is CPU share, using `docker run --cpu-shares`. 
   And we use `poolConfig.userMemory` to specify **every** `Invoker` node's memory pool size. *(Did I miss sth? Do me a favor to correct me if needed.)*
   It's easy to understand, and robust enough to fit most of the deployment case.
   
   But what if we wanna deploy `Invoker` in some resource-limited machine (eg. 4 cores CPU and 8 GB memory, only use 4 cores and 4GB memory), or K8S nodes with different CPU and memory resource?
   And How to figure out the best `userMemory` in a cluster without boiling CPUs and saving testing time, if most of the actions are CPU consuming, such as AI functions?
   
   Now I open a PR try to figure out those deploy cases, see #4648 
   
   It would use a configuration to turn on the feature, which handles better especially when K8S cluster form of different system resource nodes.
   
   Any comments are welcome.
   But I'll be on a 9 days long vocation. Sorry for the slower reply.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services