Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Cluster Interconnect Review 64 64

Posted by ScuttleMonkey
from the sparring-with-scandinavian-warriors dept.
deadline writes to tell us that Cluster Monkeys has an interesting review of cluster interconnects. From the article: "An often asked question from both 'clusters newbies' and experienced cluster users is, 'what kind of interconnects are available?' The question is important for two reasons. First, the price of interconnects can range from as little as $32 per node to as much as $3,500 per node, yet the choice of an interconnect can have a huge impact on the performance of the codes and the scalability of the codes. And second, many users are not aware of all the possibilities. People new to clusters may not know of the interconnection options and, sometimes, experienced people choose an interconnect and become fixated on it, ignoring all of the alternatives. The interconnect is an important choice and ultimately the choice depends upon on your code, requirements, and budget."
This discussion has been archived. No new comments can be posted.

Cluster Interconnect Review

Comments Filter:
  • by ScrewMaster (602015) on Saturday April 22, 2006 @04:46PM (#15181885)
    Mainly I think it's because, unlike most other stories, people are actually Reading The Fucking Article before posting. Interesting concept, eh?
  • by drmerope (771119) on Saturday April 22, 2006 @10:04PM (#15182837)
    There is a growing consensus that Infiniband is effectively a dead-end. Last year it would have been a tough call between Infiniband, Ethernet, and other more proprietary interconnects. The market seems to be favoring the backward compatibility of Ethernet, and now that low latency Ethernet (~200ns) appears to be at hand there does not appear to be any reason to prefer the less general tecnologies (Myrinet, Infiniband, etc). My friends at Myrinet hint that they are looking to using the Myrinet protocol layer on top of Ethernet and essentially EOLing the Myrinet physical layer.

    Myrinet was fabulously advanced ten years ago when it spun out of Caltech, but alas, the rest of the world has caught-up.

If you can't learn to do it well, learn to enjoy doing it badly.

Working...