[Beowulf] Infiniband modular switches
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.comFri Jun 13 12:43:31 PDT 2008
- Previous message: [Beowulf] Infiniband modular switches
- Next message: [Beowulf] Infiniband modular switches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Don, Don Holmgren wrote: > latency difference here matters to many codes). Perhaps of more > significance, though, is that you can use oversubscription to lower the > cost of your fabric. Instead of connecting 12 ports of a leaf switch to > nodes and using the other 12 ports as uplinks, you might get away with > 18 nodes and 6 uplinks, or 20 nodes and 4 uplinks. As core counts are > increasing, this is becoming more and more viable for some applications. It's important to note that the "full-bisection" touted by vendors is on paper only. In reality, static routing provides full-bisection for a very small subset of patterns, the average effective bisection on a diameter-3 Clos is ~40% of link rate (adaptive routing improves that a lot, but breaks packet order on the wire which is a requirement for some network protocols). In practice, "paper" full-bisection is near free when using a single enclosure, since all spine cables are on the backplane. For larger networks, where you have to pay for real cables to the spine level, then it may make sense to be oversubscribed if the effective bisection is already bad (static routing), or if your collective communication on large jobs are not bandwidth bounded. However, the later is often false on many-cores. Patrick
- Previous message: [Beowulf] Infiniband modular switches
- Next message: [Beowulf] Infiniband modular switches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
