[Beowulf] very low performance for very small packets under MPICH (TCP_NODELAY?)
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.
Mark Hahn hahn at physics.mcmaster.caFri Dec 30 11:11:35 PST 2005
- Previous message: [Beowulf] very low performance for very small packets under MPICH(TCP_NODELAY?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> 2.6.15) with MPI 1.2.7 and Gigabit ethernet with a 3COM Switch and > 3C2000-T NIC cards. We detected a very low efficiency in communication which appears to use the sk98lin driver. > packets or so times are in the order of 0.03~secs. This degrades the > average performance for very small packets by a factor of 100. is this measurable on real code, or only benchmarks? the reason I ask is that real code probably doesn't generate a flood of tinygrams, but the benchmark might, and if so would trigger interrupt mitigation. > Any pointers for understanding why the Nagle algorithm is still active why have you jumped to the conclusion that Nagle is at fault here?
- Previous message: [Beowulf] very low performance for very small packets under MPICH(TCP_NODELAY?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
