[Beowulf] Re: Re: Home beowulf - NIC latencies
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.
Joachim Worringen joachim at ccrl-nece.deMon Feb 14 11:18:51 PST 2005
- Previous message: [Beowulf] Re: Re: Home beowulf - NIC latencies
- Next message: [Beowulf] Re: Re: Home beowulf - NIC latencies
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Ross wrote: > Making a sequence of MPI_Isends followed by a MPI_Wait go faster than a > sequence of MPI_Sends isn't hard, particularly if the messages are to > different ranks. I would guess that every implementation will provide > better performance in the case where the user tells the implementation > about all these concurrent operations and then MPI_Waits on the bunch. In this case, the user should think about MPI_Alltoall(v) - there are MPI implementations which do this in a smarter way than Isend/Irecv/Waitall to achieve much better performance than using the naive approach. Especially if you go to large process numbers, some coordination can help a lot, even for a full bisection network like a single-stage full crossbar... Generally, collectives are there to let the library know what kind of communication is coming next. All speculations in the library based on monitoring and predicting non-collective communication will probably only do good in the matching micro-benchmark (my personal experience). Joachim -- Joachim Worringen - NEC C&C research lab St.Augustin fon +49-2241-9252.20 - fax .99 - http://www.ccrl-nece.de
- Previous message: [Beowulf] Re: Re: Home beowulf - NIC latencies
- Next message: [Beowulf] Re: Re: Home beowulf - NIC latencies
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
