In coordination with the ACCESS team, XSEDE has paused the processing of Startup, Education, and other allocation requests from August 17-31. This pause will ensure that no requests are lost while we are making infrastructure updates behind the scenes and handing things over to ACCESS. If you have questions, contact help@xsede.org. The ACCESS team will resume taking allocation requests on September 1 via https://access-ci.org/.

The discussion forums in the XSEDE User Portal are for users to share experiences, questions, and comments with other users and XSEDE staff. Visitors are welcome to browse and search, but you must login to contribute to the forums. While XSEDE staff monitor the lists, XSEDE does not guarantee that questions will be answered. Please note that the forums are not a replacement for formal support or bug reporting procedures through the XSEDE Help Desk. You must be logged in to post to the user forums.

« Back

Regarding MPI_Allgather collective calls in MPI

Combination View Flat View Tree View
Threads [ Previous | Next ]
Regarding MPI_Allgather collective calls in MPI
Answer
11/16/12 4:06 PM
The implementation of MPI_Allgather uses different algorithms internally based on the message size and number of processes. For example bruck for short messages, ring for larger messages. Why do they use different implementations? Please explain.
Flag