[Beowulf] Q: IB message rate & large core counts (per node)?
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.
Greg Lindahl lindahl at pbm.comFri Feb 19 14:17:21 PST 2010
- Previous message: [Beowulf] Q: IB message rate & large core counts (per node)?
- Next message: [Beowulf] Q: IB message rate & large core counts (per node)?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Feb 19, 2010 at 01:47:07PM -0500, Joe Landman wrote: > The big issue will be contention for the resource. Joe, What "the resource" is depends on implementation. All network cards have the limit of the line rate of the network. As far as I can tell, the Mellanox IB cards have a limited number of engines that process messages. For short messages from a lot of CPUs, they don't have enough. For long messages, they have plenty, & hit the line rate. Don't storage systems typically send mostly long messages? The InfiniPath (now True Scale) design uses a pipelined approach. You can analytically compute the performance on short messages by knowing 2 numbers: the line rate, and the "dead time" between back-to-back packets, which is determined by the length of the longest pipeline stage. I was thrilled when we figured out that our performance graph was exactly determined by that equation. And the pipeline is a resource that you can't oversubscribe. -- greg (formerly... yada yada)
- Previous message: [Beowulf] Q: IB message rate & large core counts (per node)?
- Next message: [Beowulf] Q: IB message rate & large core counts (per node)?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
