<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Another big obstacle to exascale computing: resilience</title>
	<atom:link href="http://gigaom.com/2012/03/22/resilience-problem-structure-data-2012/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2012/03/22/resilience-problem-structure-data-2012/</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 04:40:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Mark Thiele</title>
		<link>http://gigaom.com/2012/03/22/resilience-problem-structure-data-2012/#comment-822432</link>
		<dc:creator><![CDATA[Mark Thiele]]></dc:creator>
		<pubDate>Thu, 22 Mar 2012 20:34:50 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=502793#comment-822432</guid>
		<description><![CDATA[I don&#039;t understand the concern with resiliency here. With any system built to this scale, no single component should decide availability, only capacity. Unless the application is dependent on all components running all the time, which would be a very poor design strategy. Also, if specific workloads require a minimum capacity to run effectively, then you would model potential component failure rates and build that in to the total number (I.e., if 1 million is the minimum number and the yearly failure rate is 3%, then you would build to a spec of 1.03 million.)]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t understand the concern with resiliency here. With any system built to this scale, no single component should decide availability, only capacity. Unless the application is dependent on all components running all the time, which would be a very poor design strategy. Also, if specific workloads require a minimum capacity to run effectively, then you would model potential component failure rates and build that in to the total number (I.e., if 1 million is the minimum number and the yearly failure rate is 3%, then you would build to a spec of 1.03 million.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
