What is it about?

In distributed computation, it is important that all the computers used remain busy as much as possible. As it is sometimes not possible to split the work evenly, dynamic load balancers relocate part of the load from busy nodes to idle nodes during the computation. Here, we focus on the so-called "lifeline-based global load balancer." In this scheme the main procedure consists in performing a certain amount of computation (the granularity) and checking if load balancing is needed. But just how much this computation amount should be is not obvious ...

Featured Image

Why is it important?

If the granularity is too small, the load balancing procedures are performed often and redundantly, diminishing the performance of the program. On the contrary, if the granularity is too large, the load balancing procedures are seldom performed, causing the performance of the program to decrease. A just balance needs to be found. To further complicate matters, the value to use depends on the computation given to the load balancer. To resolve this issue, we introduced a tuning mechanism which automatically adjusts the granularity during execution.

Read the Original

This page is a summary of: Self-adjusting task granularity for Global load balancer library on clusters of many-core processors, February 2020, ACM (Association for Computing Machinery),
DOI: 10.1145/3380536.3380539.
You can read the full text:

Read

Resources

Contributors

The following have contributed to this page