You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/05/08 06:30:53 UTC

[GitHub] markusthoemmes commented on issue #3618: Why did you deprecate the LoadBalancerService and use ShardingContainerPoolBalancer?

markusthoemmes commented on issue #3618: Why did you deprecate the LoadBalancerService and use ShardingContainerPoolBalancer?
URL: https://github.com/apache/incubator-openwhisk/issues/3618#issuecomment-387298938
 
 
   The loadbalancing algorithm was/is the same in both loadbalancers. The "old" one used asynchronous state-sharing while the new one uses sharding.
   
   The "old" loadbalancer was deprecated and removed because under load the state-sharing was far too slow and caused loadbalancing issues. Algorithm wise, both are the same.
   
   Towards the algorithm: It is an algorithm that gives you statistical probability on warm starts. Of course we want to "fully use warm containers", that requires extending the state in the controllers + removing all scheduling logic from the invokers. We're not there yet.

----------------------------------------------------------------
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