<?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: HP Proliant DL785 G5 rocks at VMWare</title>
	<atom:link href="http://www.bladewatch.com/2008/08/26/hp-proliant-dl785-g5-rocks-at-vmware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bladewatch.com/2008/08/26/hp-proliant-dl785-g5-rocks-at-vmware/</link>
	<description>Tracking Blades, virtualization and grid</description>
	<lastBuildDate>Wed, 10 Mar 2010 06:52:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Keith</title>
		<link>http://www.bladewatch.com/2008/08/26/hp-proliant-dl785-g5-rocks-at-vmware/comment-page-1/#comment-44328</link>
		<dc:creator>Keith</dc:creator>
		<pubDate>Thu, 28 Aug 2008 02:27:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.bladewatch.com/?p=3729#comment-44328</guid>
		<description>really depends on the environment your on and how high you want to stack workloads.  i&#039;ve setup 16 node clusters with a mixture of 2 socket and 4 socket quads (Intel) and would have used 8 sockets if Intel still made them.  I started way back with a mix of DL580G2&#039;s and DL740&#039;s w ESX 2.x and had great success.  More procs; more places to schedule VM&#039;s and they can get the performance attention they ask for.</description>
		<content:encoded><![CDATA[<p>really depends on the environment your on and how high you want to stack workloads.  i&#39;ve setup 16 node clusters with a mixture of 2 socket and 4 socket quads (Intel) and would have used 8 sockets if Intel still made them.  I started way back with a mix of DL580G2&#39;s and DL740&#39;s w ESX 2.x and had great success.  More procs; more places to schedule VM&#39;s and they can get the performance attention they ask for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DGo</title>
		<link>http://www.bladewatch.com/2008/08/26/hp-proliant-dl785-g5-rocks-at-vmware/comment-page-1/#comment-44327</link>
		<dc:creator>DGo</dc:creator>
		<pubDate>Wed, 27 Aug 2008 11:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.bladewatch.com/?p=3729#comment-44327</guid>
		<description>Don&#039;t you need to weigh the options of that consolidation in terms of space, power and support in the fact that you are putting a lot of eggs in one basket.   Don&#039;t get me wrong, it&#039;s a very nice box, but say you are going to run ~96 VM&#039;s on it, what about redundancy/HA.  As my environment has grown, it has become a big concern for me.  Do I get fewer larger boxes(8 socket) and put them in a HA cluster, or spread the load out over more smaller boxes(4 socket).  I have a production cluster of three 4socket QuadCore servers with 90 VM&#039;s running in it.  Monday, one of the servers took a hit while we had a case open and HA failed to work properly.  I lost 30 vm&#039;s for little over 30 minutes.  For production, I can&#039;t see the risk, but maybe as a dev/stage environment I can see a larger box like this being useful.</description>
		<content:encoded><![CDATA[<p>Don&#39;t you need to weigh the options of that consolidation in terms of space, power and support in the fact that you are putting a lot of eggs in one basket.   Don&#39;t get me wrong, it&#39;s a very nice box, but say you are going to run ~96 VM&#39;s on it, what about redundancy/HA.  As my environment has grown, it has become a big concern for me.  Do I get fewer larger boxes(8 socket) and put them in a HA cluster, or spread the load out over more smaller boxes(4 socket).  I have a production cluster of three 4socket QuadCore servers with 90 VM&#39;s running in it.  Monday, one of the servers took a hit while we had a case open and HA failed to work properly.  I lost 30 vm&#39;s for little over 30 minutes.  For production, I can&#39;t see the risk, but maybe as a dev/stage environment I can see a larger box like this being useful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
