Charm++ parallel programming system

[Gengbin Zheng <gzheng AT illinois.edu>]

NAMD is a use case (there are some other small examples).
Hierarchical load balancer requires centralized load balancing algorithms that:

1. must use the  work() interface (instead of the strategy() interface)

2. can handle external objects that does not belong to the current processor set, e.g.  the algorithm needs to handle the case when an object in from  PE 128, while the PE set is from 0-127

3. can handle the processor's avail vector. The root processor of each processor group (or domain) is a fake processor in the sense that its availability bit is false, i.e. no object is supposed to migrate to it.

Gengbin

On Mon, May 20, 2013 at 2:03 PM, Laércio Lima Pilla <llpilla AT inf.ufrgs.br> wrote:

Greetings,

I am starting to work on a hierarchical load balancer for Charm++. 

I would like to know if there is any document with information about the usage of hierarchical load balancers, and implementation requirements related to the centralized algorithms used by a hierarchical load balancer. 

The Charm++ Manual does not touch this subject. The paper entitled "Periodic Hierarchical Load Balancing for Large Supercomputers" does not go into implementation details, nor does Gengbin's thesis.

Best regards,

--

Laércio LIMA PILLA

PhD Student at 

- Federal University of Rio Grande do Sul (UFRGS) - Brazil

- University of Grenoble - France

Email: laercio.pilla AT inf.ufrgs.br or laercio.lima.pilla AT gmail.com 
Tel: +33 (0)6 49 87 68 29
Website: www.inf.ufrgs.br/~llpilla