Charm++ parallel programming system

[Jozsef Bakosi <jbakosi AT gmail.com>]

Thanks a lot, Eric, that clears it up. I guess I'll put the heavier stuff in the map constructor then.

Jozsef

On Wed, May 20, 2015 at 8:54 AM, Eric Bohm <ebohm AT illinois.edu> wrote:

Hello Jozsef,

Procnum will be called to construct your chare, the first time a message is sent to it from a node, and each time subsequent sends do not find a precached location record for it.  The latter event can occur when many sends have pushed it out of cache, or after migration.  

The potential global memory footprint of location management caching is proportional to the total number of objects multiplied by the number of nodes.  Therefore, the runtime system keeps a finite number on each node.  At the limit, procnum could be called for nearly every message send, therefore procnum should be designed to be inexpensive. 

On 05/19/2015 09:23 AM, Jozsef Bakosi wrote:

Hi folks,

I'm trying to create an array map for custom initial placement of chare array elements.

If I create my array with 1 element on a single PE, procNum() is called twice. If I create my array with 2 elements on 2 PEs, procNum() is called 3 times for array index 0 and 4 times for array index 1. Can someone explain the mchanism behind this?

Also, is this the procNum() function called many times or just at array creation, element migration? Is it okay to put some potentially expensive calculation in there?

Thanks,

Jozsef

_______________________________________________
charm mailing list
charm AT cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/charm