<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Fat trees and skinny switches</title>
	<atom:link href="http://storagemojo.com/2008/08/24/fat-trees-and-skinny-switches/feed/" rel="self" type="application/rss+xml" />
	<link>http://storagemojo.com/2008/08/24/fat-trees-and-skinny-switches/</link>
	<description>Data storage info &#38; analysis</description>
	<lastBuildDate>Sun, 20 May 2012 13:26:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Ethernet Fabric &#171; Pronto Systems</title>
		<link>http://storagemojo.com/2008/08/24/fat-trees-and-skinny-switches/comment-page-1/#comment-215020</link>
		<dc:creator>Ethernet Fabric &#171; Pronto Systems</dc:creator>
		<pubDate>Sat, 12 Feb 2011 18:37:19 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=895#comment-215020</guid>
		<description>[...] have seen a lot of discussions on the benefit of fabric architecture, including higher bandwidth, lower latency, lower cost, and [...]</description>
		<content:encoded><![CDATA[<p>[...] have seen a lot of discussions on the benefit of fabric architecture, including higher bandwidth, lower latency, lower cost, and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Jones</title>
		<link>http://storagemojo.com/2008/08/24/fat-trees-and-skinny-switches/comment-page-1/#comment-197276</link>
		<dc:creator>Steve Jones</dc:creator>
		<pubDate>Tue, 26 Aug 2008 08:02:49 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=895#comment-197276</guid>
		<description>The price parity between 10 bytes of network traffic, and 1 MB of disk bandwidth refers to WAN network, not LAN. As the article refers to data centre articles, I&#039;m not sure of the relevance. Indeed if you read the distributed computing economics paper, then it has price parity between LAN and disk bandwidth (about 1TB per $).  For data centres that&#039;s not suprising - big iron SAN switches and LAN switches are both expensive items. In many cases, it&#039;s even the same basic frames. That&#039;s not to say that there isn&#039;t some potential value in using commodity switches for some types of connection, but the reality of many data centres is that extensive use is made of network virtualisation in SAN and Ethernet connections. commodity switches generally can&#039;t do those sort of things.

As for the energy consumption per GBps and trhe heat dissipation, the chart shows an approximate 3:1 reduction for both. That&#039;s hardly suprising - unless something has gone seriously wrong with the law of conservation of energy (or somehow a very large proportion of the &quot;big iron&quot; switches&#039; power is being disipated in the form of electro-magnetic radiation outside the data centre (hardly likely) then pretty well all that electrical energy eventually comes out as heat. (Yes, there are a few little niceties about power factors, reactive loads and the like, but generally electrical power in = heat out to a very close order in a closed environment).</description>
		<content:encoded><![CDATA[<p>The price parity between 10 bytes of network traffic, and 1 MB of disk bandwidth refers to WAN network, not LAN. As the article refers to data centre articles, I&#8217;m not sure of the relevance. Indeed if you read the distributed computing economics paper, then it has price parity between LAN and disk bandwidth (about 1TB per $).  For data centres that&#8217;s not suprising &#8211; big iron SAN switches and LAN switches are both expensive items. In many cases, it&#8217;s even the same basic frames. That&#8217;s not to say that there isn&#8217;t some potential value in using commodity switches for some types of connection, but the reality of many data centres is that extensive use is made of network virtualisation in SAN and Ethernet connections. commodity switches generally can&#8217;t do those sort of things.</p>
<p>As for the energy consumption per GBps and trhe heat dissipation, the chart shows an approximate 3:1 reduction for both. That&#8217;s hardly suprising &#8211; unless something has gone seriously wrong with the law of conservation of energy (or somehow a very large proportion of the &#8220;big iron&#8221; switches&#8217; power is being disipated in the form of electro-magnetic radiation outside the data centre (hardly likely) then pretty well all that electrical energy eventually comes out as heat. (Yes, there are a few little niceties about power factors, reactive loads and the like, but generally electrical power in = heat out to a very close order in a closed environment).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bofkentucky</title>
		<link>http://storagemojo.com/2008/08/24/fat-trees-and-skinny-switches/comment-page-1/#comment-197272</link>
		<dc:creator>bofkentucky</dc:creator>
		<pubDate>Mon, 25 Aug 2008 22:55:59 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=895#comment-197272</guid>
		<description>Check out http://aggregate.org/FNN/ for more research on maximizing bisection bandwidth while controlling per-port costs for clusters.</description>
		<content:encoded><![CDATA[<p>Check out <a href="http://aggregate.org/FNN/" rel="nofollow">http://aggregate.org/FNN/</a> for more research on maximizing bisection bandwidth while controlling per-port costs for clusters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Som</title>
		<link>http://storagemojo.com/2008/08/24/fat-trees-and-skinny-switches/comment-page-1/#comment-197270</link>
		<dc:creator>Som</dc:creator>
		<pubDate>Mon, 25 Aug 2008 17:59:59 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=895#comment-197270</guid>
		<description>You can achieve the same using existing switches using ECMP. The first level switches do not even need to run IP - they can be L2 switches.  

HPC clusters have been using two and multi-layer CLOS configuration for at least seven/eight years.

What&#039;s the benefit of the two level routing table scheme?
( I have not gone through the full paper yet - I hope to do that shortly - maybe the answer will be obvious)

Som Sikdar</description>
		<content:encoded><![CDATA[<p>You can achieve the same using existing switches using ECMP. The first level switches do not even need to run IP &#8211; they can be L2 switches.  </p>
<p>HPC clusters have been using two and multi-layer CLOS configuration for at least seven/eight years.</p>
<p>What&#8217;s the benefit of the two level routing table scheme?<br />
( I have not gone through the full paper yet &#8211; I hope to do that shortly &#8211; maybe the answer will be obvious)</p>
<p>Som Sikdar</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amin Vahdat</title>
		<link>http://storagemojo.com/2008/08/24/fat-trees-and-skinny-switches/comment-page-1/#comment-197269</link>
		<dc:creator>Amin Vahdat</dc:creator>
		<pubDate>Mon, 25 Aug 2008 14:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=895#comment-197269</guid>
		<description>Thank you very much for your note and for the article.  I think that the article is well done.  As co-author of the original article, I have a few comments:
- You mention that &quot;The power efficiency argument is not going to be that persuasive. The real win is in the dollars.&quot; I would argue that, if you care to, you can reduce the power efficiency argument to dollars.  For PC&#039;s in a data center, the cost to cool the machines dominates the hardware cost over a 2-3 year period. There will be increasing pressure on the IT industry both from within (dollars) and without (carbon footprint, regulation, etc.) to limit energy usage.
- You describe a &quot;maximum capacity 27,648 node cluster using 48 port switches&quot;.  In fact, we based most of our discussion on 48-port switches because they currently offer the most performance per dollar and are a good match to current rack sizes in the data center.  However, one could use 64-port switches in a fat tree topology to build out a 65,536 node cluster or 96-port switches to build out a 221,184 node cluster.  One nice property of a fat tree is that the number of hosts that it supports grows with the cube of the number of ports in the baseline switching element.  More specifically, using k-port switches, a fat tree can support (k^3)/4 hosts.
- Finally, I think that one of the compelling arguments for this approach is that it does not rely upon aggregation to higher speed links to achieve its scale (relative to traditional tree-based techniques).  Thus, if you wanted to build out a cluster with 10 GigE all the way to the edge servers, you would not have any options today using traditional techniques because there is no standard for higher-speed Ethernet (e.g., 40 GigE) yet available.  Even when it does become available, available switches will have low port density and, typically, prohibitive costs.  The fat tree approach uses identical switching elements throughout the structure, meaning that it could deliver 10GigE to the edge even today.</description>
		<content:encoded><![CDATA[<p>Thank you very much for your note and for the article.  I think that the article is well done.  As co-author of the original article, I have a few comments:<br />
- You mention that &#8220;The power efficiency argument is not going to be that persuasive. The real win is in the dollars.&#8221; I would argue that, if you care to, you can reduce the power efficiency argument to dollars.  For PC&#8217;s in a data center, the cost to cool the machines dominates the hardware cost over a 2-3 year period. There will be increasing pressure on the IT industry both from within (dollars) and without (carbon footprint, regulation, etc.) to limit energy usage.<br />
- You describe a &#8220;maximum capacity 27,648 node cluster using 48 port switches&#8221;.  In fact, we based most of our discussion on 48-port switches because they currently offer the most performance per dollar and are a good match to current rack sizes in the data center.  However, one could use 64-port switches in a fat tree topology to build out a 65,536 node cluster or 96-port switches to build out a 221,184 node cluster.  One nice property of a fat tree is that the number of hosts that it supports grows with the cube of the number of ports in the baseline switching element.  More specifically, using k-port switches, a fat tree can support (k^3)/4 hosts.<br />
- Finally, I think that one of the compelling arguments for this approach is that it does not rely upon aggregation to higher speed links to achieve its scale (relative to traditional tree-based techniques).  Thus, if you wanted to build out a cluster with 10 GigE all the way to the edge servers, you would not have any options today using traditional techniques because there is no standard for higher-speed Ethernet (e.g., 40 GigE) yet available.  Even when it does become available, available switches will have low port density and, typically, prohibitive costs.  The fat tree approach uses identical switching elements throughout the structure, meaning that it could deliver 10GigE to the edge even today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin Harris</title>
		<link>http://storagemojo.com/2008/08/24/fat-trees-and-skinny-switches/comment-page-1/#comment-197267</link>
		<dc:creator>Robin Harris</dc:creator>
		<pubDate>Mon, 25 Aug 2008 07:29:59 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=895#comment-197267</guid>
		<description>Anon,

You&#039;ve noted a &quot;wordo&quot; - an artifact of learning to write with my mouth. 

I&#039;ve started using dictation software. The spelling is good, but it misses entire words and I haven&#039;t yet figured out how to catch those.

Please bear with me.

Robin</description>
		<content:encoded><![CDATA[<p>Anon,</p>
<p>You&#8217;ve noted a &#8220;wordo&#8221; &#8211; an artifact of learning to write with my mouth. </p>
<p>I&#8217;ve started using dictation software. The spelling is good, but it misses entire words and I haven&#8217;t yet figured out how to catch those.</p>
<p>Please bear with me.</p>
<p>Robin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://storagemojo.com/2008/08/24/fat-trees-and-skinny-switches/comment-page-1/#comment-197264</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 25 Aug 2008 03:00:47 +0000</pubDate>
		<guid isPermaLink="false">http://storagemojo.com/?p=895#comment-197264</guid>
		<description>&quot;fat tree&quot;? &quot;fact tree&quot;? Which is it?</description>
		<content:encoded><![CDATA[<p>&#8220;fat tree&#8221;? &#8220;fact tree&#8221;? Which is it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

