<?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: CTR&#8217;s 2009 top 5 trends in HPC</title>
	<atom:link href="http://insidehpc.com/2009/02/22/ctrs-2009-top-5-trends-in-hpc/feed/" rel="self" type="application/rss+xml" />
	<link>http://insidehpc.com/2009/02/22/ctrs-2009-top-5-trends-in-hpc/</link>
	<description>HPC news for supercomputing professionals</description>
	<lastBuildDate>Mon, 21 May 2012 17:48:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Joe</title>
		<link>http://insidehpc.com/2009/02/22/ctrs-2009-top-5-trends-in-hpc/comment-page-1/#comment-150476</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Mon, 23 Feb 2009 22:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=3807#comment-150476</guid>
		<description>Whoops, my bad.  I had mis-understood what you meant.  I think we are in close agreement. 

Must .... not .... post .... before .... coffee ....</description>
		<content:encoded><![CDATA[<p>Whoops, my bad.  I had mis-understood what you meant.  I think we are in close agreement. </p>
<p>Must &#8230;. not &#8230;. post &#8230;. before &#8230;. coffee &#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John West</title>
		<link>http://insidehpc.com/2009/02/22/ctrs-2009-top-5-trends-in-hpc/comment-page-1/#comment-150439</link>
		<dc:creator>John West</dc:creator>
		<pubDate>Mon, 23 Feb 2009 19:09:33 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=3807#comment-150439</guid>
		<description>Joe - I agree entirely about GPUs (for now at least). My &quot;general accelerator&quot; comment was meant to be limited to the GPU parent class, including Clearspeed and FPGAs and whatnot. I was trying to convey with my next sentence &quot;But GPUs look like they are going to run in 2009...&quot; that I think GPUs are the specific exception to the general rule...but I think I failed to be clear!</description>
		<content:encoded><![CDATA[<p>Joe &#8211; I agree entirely about GPUs (for now at least). My &#8220;general accelerator&#8221; comment was meant to be limited to the GPU parent class, including Clearspeed and FPGAs and whatnot. I was trying to convey with my next sentence &#8220;But GPUs look like they are going to run in 2009&#8230;&#8221; that I think GPUs are the specific exception to the general rule&#8230;but I think I failed to be clear!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://insidehpc.com/2009/02/22/ctrs-2009-top-5-trends-in-hpc/comment-page-1/#comment-150430</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Mon, 23 Feb 2009 18:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=3807#comment-150430</guid>
		<description>Hi John:

  I disagree with the comment &quot;the general accelerator rush is coming to an end&quot;.  On the contrary, speaking with customers, it seems to be picking up.  Clearspeed had issues as a company and as a product, but they are/were not the only accelerator provider.

  The argument for accelerators is compelling for the smaller users in terms of leveraging power to their applications.  It is compelling for the software ISV&#039;s looking to help their customers decrease the cost of their hardware in order to have more budget for the ISV&#039;s software.  

  Accelerators offer some combination of many more processor cycles per wallclock tick, or more efficient cycles per wallclock tick.  As we demonstrated recently with GPU-HMMer, a single machine with 3 GPUs can outperform a more power-hungry/harder to maintain cluster on the same code.  That is, there is a financial, ease of use, and believe it or not, a green argument to be made for using accelerators.  As you note in the subsequent article, the memory wall is a problem, and curiously enough the GPUs suffer from their own version of it, though it is ~10x further out than the memory wall on the host (what we call computing substrate). 

  Clearspeed failed due to them having a business model that required ~$5k/accelerator for ~10x wallclock on ordinary applications, where your code needed to be ported, and Clearspeed accelerators were not ubiquitous.  Programmable GPUs are in 1E+7 devices, cost from $150-$1800/unit, giving 5-30x per application (not per kernel).  Couple this ubiquity with the low cost (I can/do develop Cuda code on my laptop) of the platform and the zero cost of the tools, and you have something of interest for people in need of ever more computing capability with an ever decreasing budget for the same.

 We might have to agree to disagree, but accelerators appear to have a very bright, and long future ahead of them in HPC.

Joe</description>
		<content:encoded><![CDATA[<p>Hi John:</p>
<p>  I disagree with the comment &#8220;the general accelerator rush is coming to an end&#8221;.  On the contrary, speaking with customers, it seems to be picking up.  Clearspeed had issues as a company and as a product, but they are/were not the only accelerator provider.</p>
<p>  The argument for accelerators is compelling for the smaller users in terms of leveraging power to their applications.  It is compelling for the software ISV&#8217;s looking to help their customers decrease the cost of their hardware in order to have more budget for the ISV&#8217;s software.  </p>
<p>  Accelerators offer some combination of many more processor cycles per wallclock tick, or more efficient cycles per wallclock tick.  As we demonstrated recently with GPU-HMMer, a single machine with 3 GPUs can outperform a more power-hungry/harder to maintain cluster on the same code.  That is, there is a financial, ease of use, and believe it or not, a green argument to be made for using accelerators.  As you note in the subsequent article, the memory wall is a problem, and curiously enough the GPUs suffer from their own version of it, though it is ~10x further out than the memory wall on the host (what we call computing substrate). </p>
<p>  Clearspeed failed due to them having a business model that required ~$5k/accelerator for ~10x wallclock on ordinary applications, where your code needed to be ported, and Clearspeed accelerators were not ubiquitous.  Programmable GPUs are in 1E+7 devices, cost from $150-$1800/unit, giving 5-30x per application (not per kernel).  Couple this ubiquity with the low cost (I can/do develop Cuda code on my laptop) of the platform and the zero cost of the tools, and you have something of interest for people in need of ever more computing capability with an ever decreasing budget for the same.</p>
<p> We might have to agree to disagree, but accelerators appear to have a very bright, and long future ahead of them in HPC.</p>
<p>Joe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scalability.org &#187; Blog Archive &#187; &#8220;Top HPC trends&#8221; &#8230; or are they?</title>
		<link>http://insidehpc.com/2009/02/22/ctrs-2009-top-5-trends-in-hpc/comment-page-1/#comment-150371</link>
		<dc:creator>scalability.org &#187; Blog Archive &#187; &#8220;Top HPC trends&#8221; &#8230; or are they?</dc:creator>
		<pubDate>Mon, 23 Feb 2009 12:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=3807#comment-150371</guid>
		<description>[...] West at InsideHPC.com links to an article I read last week and didn&#8217;t comment on. In this article David Driggers, CTO at Verari, points [...]</description>
		<content:encoded><![CDATA[<p>[...] West at InsideHPC.com links to an article I read last week and didn&#8217;t comment on. In this article David Driggers, CTO at Verari, points [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

