charm AT lists.siebelschool.illinois.edu
Subject: Charm++ parallel programming system
List archive
Re: [charm] Scalable creation of chare array elements, passing a different portion of a potentially large array to their constructors
Chronological Thread
- From: Jozsef Bakosi <jbakosi AT gmail.com>
- To: "Kale, Laxmikant V" <kale AT illinois.edu>
- Cc: "charm AT cs.uiuc.edu" <charm AT cs.uiuc.edu>
- Subject: Re: [charm] Scalable creation of chare array elements, passing a different portion of a potentially large array to their constructors
- Date: Mon, 2 Nov 2015 12:01:00 -0700
Hi folks,
After reading the papers at http://charm.cs.illinois.edu/research/msa and the thesis at https://charm.cs.illinois.edu/newPapers/05-05/paper.pdf, though may not exactly have been designed for my use case, it looks like what I need could also be done using multiphase shared arrays (MSA).
In particular, the thesis above says: "MSA also allows us to set a cap on the memory used per processor. Thus it can be used to read in a huge amount of data on one processor but store it simply and efficiently across other processors." This seems like exactly what I need. Even if this is not very efficient, since I only need to do this once during setup, I think this should work and would be better than saving many small files and re-reading them by chares. In fact, I would already be happy if creating many chares, initialized by chunks of the large data in alldata, would survive without blowing out of communication buffers with, say 100K+ CPUs.
Does anyone think MSA is NOT okay for this purpose?
Jozsef
- Re: [charm] Scalable creation of chare array elements, passing a different portion of a potentially large array to their constructors, Jozsef Bakosi, 11/02/2015
- <Possible follow-up(s)>
- Re: [charm] Scalable creation of chare array elements, passing a different portion of a potentially large array to their constructors, Jozsef Bakosi, 11/13/2015
Archive powered by MHonArc 2.6.16.