<?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"
	>
<channel>
	<title>Comments on: Data centre heating effects</title>
	<atom:link href="http://www.openxtra.co.uk/blog/data-centre-heating-effects/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.openxtra.co.uk/blog/data-centre-heating-effects/</link>
	<description>Your daily IT cuppa</description>
	<pubDate>Tue, 14 Oct 2008 00:12:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Jack Hughes</title>
		<link>http://www.openxtra.co.uk/blog/data-centre-heating-effects/#comment-5465</link>
		<dc:creator>Jack Hughes</dc:creator>
		<pubDate>Mon, 10 Dec 2007 13:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.openxtra.co.uk/blog/data-centre-heating-effects/#comment-5465</guid>
		<description>@Ronald - thanks for dropping by. With Intel's new experimental prototype the POLARIS chip generating 260 Watts @ 5.6 GHz, it's hard to see the problem getting much easier anytime soon. ;)</description>
		<content:encoded><![CDATA[<p>@Ronald - thanks for dropping by. With Intel&#8217;s new experimental prototype the POLARIS chip generating 260 Watts @ 5.6 GHz, it&#8217;s hard to see the problem getting much easier anytime soon. <img src='http://www.openxtra.co.uk/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronald</title>
		<link>http://www.openxtra.co.uk/blog/data-centre-heating-effects/#comment-5464</link>
		<dc:creator>Ronald</dc:creator>
		<pubDate>Mon, 10 Dec 2007 12:52:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.openxtra.co.uk/blog/data-centre-heating-effects/#comment-5464</guid>
		<description>This is true as I recently experienced a similar situation.  The temperature starts to rise so that it is noticeable by a person within 5 minutes and within 45 minutes you could cook eggs.
But servers should not suffer irreparable damage?  All modern servers have settings to do a critical shutdown on high temperature.  In the situation above, some servers started shutting down after 30 minutes.
The solution and cause is not that complex as the Rackspace annoucement makes it out to be.  I assume Rackspace has the same issue.
1. Chillers aren't connected to UPS.  They draw to much juice!  They are powered in a failure by generator power.  The UPS is there for the server and communications equipment.
2. The Chiller controller's must be wired to UPS!!!  The controller starts the chiller, monitors is function, temp, etc, etc.  If the chiller controller is on generator power as well then the startup happens incorrectly.
3. The Chiller startup needs to be staggered. If you have 10 chillers starting at once they overload the generator which then protects its circuits and the chillers cycle.  Switching everything on at once is not a good idea due to the power spike - Do you remember the scene in Apollo 13 where Mattingly had to experiment to perfect the power-on sequencing of the LEM?  Same thing.
4. The chiller startup is time staggered (even more reason to have the controller on UPS).  The chillers are started in batches every 5 minutes.  The chillers in the batch should be not be 2 chillers next to each other or a portion of the data centre might hot spot if that area has a chiller batch that is the last to start up.</description>
		<content:encoded><![CDATA[<p>This is true as I recently experienced a similar situation.  The temperature starts to rise so that it is noticeable by a person within 5 minutes and within 45 minutes you could cook eggs.<br />
But servers should not suffer irreparable damage?  All modern servers have settings to do a critical shutdown on high temperature.  In the situation above, some servers started shutting down after 30 minutes.<br />
The solution and cause is not that complex as the Rackspace annoucement makes it out to be.  I assume Rackspace has the same issue.<br />
1. Chillers aren&#8217;t connected to UPS.  They draw to much juice!  They are powered in a failure by generator power.  The UPS is there for the server and communications equipment.<br />
2. The Chiller controller&#8217;s must be wired to UPS!!!  The controller starts the chiller, monitors is function, temp, etc, etc.  If the chiller controller is on generator power as well then the startup happens incorrectly.<br />
3. The Chiller startup needs to be staggered. If you have 10 chillers starting at once they overload the generator which then protects its circuits and the chillers cycle.  Switching everything on at once is not a good idea due to the power spike - Do you remember the scene in Apollo 13 where Mattingly had to experiment to perfect the power-on sequencing of the LEM?  Same thing.<br />
4. The chiller startup is time staggered (even more reason to have the controller on UPS).  The chillers are started in batches every 5 minutes.  The chillers in the batch should be not be 2 chillers next to each other or a portion of the data centre might hot spot if that area has a chiller batch that is the last to start up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
