[Beowulf] Performance tuning for Jumbo Frames
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.comSat Dec 12 10:45:35 PST 2009
- Previous message: [Beowulf] Performance tuning for Jumbo Frames
- Next message: [Beowulf] Performance tuning for Jumbo Frames
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Richard, richard.walsh at comcast.net wrote: > I would seem that a larger MTU would help in at least two situations, > clearly applications with very large messages, but also those that > have transmission bursts of messages below the MTU that could > take advantage of hardware coalescing. Such coalescing is typically not done in hardware. TCP with Nagle will coalesce small messages going to the same destination. However, Nagle trades latency for bandwidth, so latency junkies such as HPC apps often disable Nagle when using TCP. Some MPI implementations do coalesce small messages, mainly to look good on packet rate benchmarks. > The common MTU of 1500 was not chosen arbitrarily, Never underestimate what a standard committee can do. Patrick
- Previous message: [Beowulf] Performance tuning for Jumbo Frames
- Next message: [Beowulf] Performance tuning for Jumbo Frames
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
