[Beowulf] Why is communication so expensive for very small messages?
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.comTue Apr 24 12:54:42 PDT 2007
- Previous message: [Beowulf] Why is communication so expensive for very small messages?
- Next message: [Beowulf] scheduler policy design
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jonathan Boyle wrote: > For 2 processor blocking calls, mpptest indicates a latency of about 30 > microseconds. > > However when I measure communication times in my own program using a loop as > follows.... If you don't want flow control problems, you need to do a pingpong (each node send and recv alternatively) or do explicit flow control using a window nad ack message. MPI_Send() can return as soon as the data is buffered (ie copied somewhere on the send side), and that is much faster than the network itself, so the somewhere will fill up eventually. Patrick
- Previous message: [Beowulf] Why is communication so expensive for very small messages?
- Next message: [Beowulf] scheduler policy design
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
