MetaLB: Separate cost/benefit analysis for running LB strategy and performing migration
MetaLB potentially has two separate decisions to make as execution proceeds:
1. Is current load imbalance bad enough to justify the cost of running the load balancing strategy to compute new assignments?
2. Having obtained new better-balanced assignments, is the improvement they would offer enough to justify the cost of migration they would entail?
We may need to carry object size information (as reported by the sizing PUPper) in the load balancing database to allow estimation of migration costs as soon as decisions are made. Alternately, we can transmit the decisions and compute the expected time cost in a distributed fashion (max over network model, some more detailed contention-based estimate, simulation, etc.).
#5 Updated by Kavitha Chandrasekar about 1 year ago
Estimation of migration costs is already included in the model based method to select Load balancing strategy. So this issue is somewaht subsumed by https://charm.cs.illinois.edu/gerrit/#/c/charm/+/1914/