<?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:go='http://ns.gigaom.com/'
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: Google Gets Shifty With Its Data Center Operations</title>
	<atom:link href="http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 00:50:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: AT&#38;T Dials Up a Computing Cloud &#8211; GigaOM</title>
		<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/#comment-217832</link>
		<dc:creator><![CDATA[AT&#38;T Dials Up a Computing Cloud &#8211; GigaOM]]></dc:creator>
		<pubDate>Fri, 20 Nov 2009 05:07:56 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59300#comment-217832</guid>
		<description><![CDATA[&lt;p&gt;[...] needs. AT&amp;T&#8217;s eventual goal (a common one in the industry) is to enable customers to move their computing around the world either following demand, lower power prices or whatever makes sense for the customer. AT&amp;T may [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] needs. AT&amp;T&#8217;s eventual goal (a common one in the industry) is to enable customers to move their computing around the world either following demand, lower power prices or whatever makes sense for the customer. AT&amp;T may [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Few &#8220;Techie&#8221; Links of Interest, 21 July 2009</title>
		<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/#comment-217831</link>
		<dc:creator><![CDATA[A Few &#8220;Techie&#8221; Links of Interest, 21 July 2009]]></dc:creator>
		<pubDate>Tue, 21 Jul 2009 15:33:36 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59300#comment-217831</guid>
		<description><![CDATA[[...] talks about how Google can shift operations from one data center to another half-way around the globe, during [...]]]></description>
		<content:encoded><![CDATA[<p>[...] talks about how Google can shift operations from one data center to another half-way around the globe, during [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hari Balakrishnan</title>
		<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/#comment-217830</link>
		<dc:creator><![CDATA[Hari Balakrishnan]]></dc:creator>
		<pubDate>Fri, 17 Jul 2009 22:25:31 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59300#comment-217830</guid>
		<description><![CDATA[Apologies in advance for the shameless self-promotion.  We have recently looked at this idea in a research project at MIT, done with some collaborators from Akamai.  Our recent paper analyzes such strategies from the standpoint of electricity cost savings.  The paper, titled &quot;Cutting the Electric Bill for Internet-Scale Systems&quot;, will appear at the SIGCOMM networking conference.  The paper is at http://nms.lcs.mit.edu/papers/index.php?detail=190 for those of you who want to see some analysis (there are definitely some idealizations and assumptions, but we believe that the analysis is generally sound).  The paper also contains a number of useful references.

The abstract of the paper is as follows: Energy expenses are becoming an increasingly important fraction of data center operating costs. At the same time, the energy expense per unit of computation can vary significantly
between two different locations. In this paper, we characterize the variation due to fluctuating electricity
prices and argue that existing distributed systems should be able to exploit this variation for significant economic gains. Electricity prices exhibit both temporal and geographic variation, due to regional demand differences, transmission inefficiencies, and generation diversity. Starting with historical electricity prices for twenty nine locations in the US, and network traffic data collected on Akamai’s CDN, we use simulation to quantify the possible economic gains for a realistic workload. Our results imply that existing systems may be able to save millions of dollars a year in electricity costs by being cognizant of locational computation cost differences.]]></description>
		<content:encoded><![CDATA[<p>Apologies in advance for the shameless self-promotion.  We have recently looked at this idea in a research project at MIT, done with some collaborators from Akamai.  Our recent paper analyzes such strategies from the standpoint of electricity cost savings.  The paper, titled &#8220;Cutting the Electric Bill for Internet-Scale Systems&#8221;, will appear at the SIGCOMM networking conference.  The paper is at <a href="http://nms.lcs.mit.edu/papers/index.php?detail=190" rel="nofollow">http://nms.lcs.mit.edu/papers/index.php?detail=190</a> for those of you who want to see some analysis (there are definitely some idealizations and assumptions, but we believe that the analysis is generally sound).  The paper also contains a number of useful references.</p>
<p>The abstract of the paper is as follows: Energy expenses are becoming an increasingly important fraction of data center operating costs. At the same time, the energy expense per unit of computation can vary significantly<br />
between two different locations. In this paper, we characterize the variation due to fluctuating electricity<br />
prices and argue that existing distributed systems should be able to exploit this variation for significant economic gains. Electricity prices exhibit both temporal and geographic variation, due to regional demand differences, transmission inefficiencies, and generation diversity. Starting with historical electricity prices for twenty nine locations in the US, and network traffic data collected on Akamai’s CDN, we use simulation to quantify the possible economic gains for a realistic workload. Our results imply that existing systems may be able to save millions of dollars a year in electricity costs by being cognizant of locational computation cost differences.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eideard</title>
		<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/#comment-217829</link>
		<dc:creator><![CDATA[Eideard]]></dc:creator>
		<pubDate>Fri, 17 Jul 2009 15:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59300#comment-217829</guid>
		<description><![CDATA[The core problem with that analysis was that it was based on how Microsoft would go about accomplishing that.  Then.]]></description>
		<content:encoded><![CDATA[<p>The core problem with that analysis was that it was based on how Microsoft would go about accomplishing that.  Then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Creswell</title>
		<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/#comment-217828</link>
		<dc:creator><![CDATA[Dan Creswell]]></dc:creator>
		<pubDate>Fri, 17 Jul 2009 12:07:42 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59300#comment-217828</guid>
		<description><![CDATA[IMHO Google are already well advanced in handling these issues as they&#039;re closely related to general failure handling/loss of a data-centre.  Many useful details can be found in the papers they already publish but the recent problem around AppEngine and the associated post-mortem reveals quite a lot more:

http://groups.google.com/group/google-appengine/msg/ba95ded980c8c179?pli=1]]></description>
		<content:encoded><![CDATA[<p>IMHO Google are already well advanced in handling these issues as they&#8217;re closely related to general failure handling/loss of a data-centre.  Many useful details can be found in the papers they already publish but the recent problem around AppEngine and the associated post-mortem reveals quite a lot more:</p>
<p><a href="http://groups.google.com/group/google-appengine/msg/ba95ded980c8c179?pli=1" rel="nofollow">http://groups.google.com/group/google-appengine/msg/ba95ded980c8c179?pli=1</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sujit Mohanty</title>
		<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/#comment-217827</link>
		<dc:creator><![CDATA[Sujit Mohanty]]></dc:creator>
		<pubDate>Fri, 17 Jul 2009 04:09:11 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59300#comment-217827</guid>
		<description><![CDATA[Cassatt did this as their sole focus, and still they never got it right. In internal data centers and hybrid private / public cloud models, the biggest headache is automation that can handle the underlying infrastructure. Its a much more difficult task than it seems to the casual observer. We&#039;re about two years out before major companies have fully deployed solutions attacking this problem, and at that point we probably would have barely tapped the surface.]]></description>
		<content:encoded><![CDATA[<p>Cassatt did this as their sole focus, and still they never got it right. In internal data centers and hybrid private / public cloud models, the biggest headache is automation that can handle the underlying infrastructure. Its a much more difficult task than it seems to the casual observer. We&#8217;re about two years out before major companies have fully deployed solutions attacking this problem, and at that point we probably would have barely tapped the surface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren</title>
		<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/#comment-217826</link>
		<dc:creator><![CDATA[Darren]]></dc:creator>
		<pubDate>Fri, 17 Jul 2009 01:44:02 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59300#comment-217826</guid>
		<description><![CDATA[@vijay you should post a link to that paper]]></description>
		<content:encoded><![CDATA[<p>@vijay you should post a link to that paper</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vijaygill</title>
		<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/#comment-217825</link>
		<dc:creator><![CDATA[vijaygill]]></dc:creator>
		<pubDate>Thu, 16 Jul 2009 20:57:34 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59300#comment-217825</guid>
		<description><![CDATA[I believe that the cost structure of this is worth analyzing - Microsoft has a good paper on this, basically the summary is that unless you need to touch the data with more than a few hundred thousand cycles worth of CPU, it is not worth it to move the data. You can trade off data transport cost, cpu cycle, environmentals.
So it is not quite as simple as follow the moon above.

/vijay]]></description>
		<content:encoded><![CDATA[<p>I believe that the cost structure of this is worth analyzing &#8211; Microsoft has a good paper on this, basically the summary is that unless you need to touch the data with more than a few hundred thousand cycles worth of CPU, it is not worth it to move the data. You can trade off data transport cost, cpu cycle, environmentals.<br />
So it is not quite as simple as follow the moon above.</p>
<p>/vijay</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Stein</title>
		<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/#comment-217824</link>
		<dc:creator><![CDATA[Greg Stein]]></dc:creator>
		<pubDate>Thu, 16 Jul 2009 20:46:33 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59300#comment-217824</guid>
		<description><![CDATA[Regarding the &quot;lots of bandwitdh needed&quot; ... remember Google buying up all that dark fiber years ago? :-)]]></description>
		<content:encoded><![CDATA[<p>Regarding the &#8220;lots of bandwitdh needed&#8221; &#8230; remember Google buying up all that dark fiber years ago? :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey</title>
		<link>http://gigaom.com/2009/07/16/google-gets-shifty-with-its-data-center-operations/#comment-217823</link>
		<dc:creator><![CDATA[Jeffrey]]></dc:creator>
		<pubDate>Thu, 16 Jul 2009 18:37:25 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=59300#comment-217823</guid>
		<description><![CDATA[Yeah, it&#039;s easier to move solar power around than would be to move cold air around.]]></description>
		<content:encoded><![CDATA[<p>Yeah, it&#8217;s easier to move solar power around than would be to move cold air around.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

