<?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: The dangers of a monoculture for the future of HPC</title>
	<atom:link href="http://insidehpc.com/2009/01/05/the-dangers-of-a-monoculture-for-the-future-of-hpc/feed/" rel="self" type="application/rss+xml" />
	<link>http://insidehpc.com/2009/01/05/the-dangers-of-a-monoculture-for-the-future-of-hpc/</link>
	<description>HPC news for supercomputing professionals</description>
	<lastBuildDate>Tue, 07 Feb 2012 16:32:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: AlStutz</title>
		<link>http://insidehpc.com/2009/01/05/the-dangers-of-a-monoculture-for-the-future-of-hpc/comment-page-1/#comment-135580</link>
		<dc:creator>AlStutz</dc:creator>
		<pubDate>Wed, 07 Jan 2009 16:40:36 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/?p=3421#comment-135580</guid>
		<description>CPU diversity is essential. But we still are focusing on the easiest thing to attack. More compute power! How many cycles do we throw away everyday because we aren’t investing enough in basic compiler development, code optimization or the biggest issue data movement. How much productivity and cpu cycles are  loss in the current applications software companies licensing methodology?</description>
		<content:encoded><![CDATA[<p>CPU diversity is essential. But we still are focusing on the easiest thing to attack. More compute power! How many cycles do we throw away everyday because we aren’t investing enough in basic compiler development, code optimization or the biggest issue data movement. How much productivity and cpu cycles are  loss in the current applications software companies licensing methodology?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

