[Beowulf] Performance characterising a HPC application
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Patrick Geoffray patrick at myri.comWed Mar 28 22:43:43 PDT 2007
- Previous message: [Beowulf] Performance characterising a HPC application
- Next message: [Beowulf] Performance characterising a HPC application
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Richard, Richard Walsh wrote: > It is useful in a message context in the same way the vector > instructions are useful in a memory > reference context. Automatic "message" aggregation is an > optimization technique being > used in UPC compiler development. Message aggregation would be much more beneficial in the context of UPC, where the compiler will likely generates many small grain communications to the same remote process. However, as Greg pointed out, MPI applications often already aggregate messages themselves (this is something even "challenged" application people understand easily). I would bet that UPC could more efficiently leverage a strided or vector communication primitive instead of message aggregation. I don't know if GasNet provides one, I know ARMCI does. Patrick -- Patrick Geoffray Myricom, Inc. http://www.myri.com
- Previous message: [Beowulf] Performance characterising a HPC application
- Next message: [Beowulf] Performance characterising a HPC application
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
