<?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: ESX Memory Management: Ballooning Rules</title>
	<atom:link href="http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/feed/" rel="self" type="application/rss+xml" />
	<link>http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/</link>
	<description>Scott Drummonds on Virtualization</description>
	<lastBuildDate>Thu, 02 Feb 2012 12:54:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Gabes Virtual World &#187; Memory overcommit in production? YES YES YES</title>
		<link>http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/comment-page-1/#comment-3354</link>
		<dc:creator>Gabes Virtual World &#187; Memory overcommit in production? YES YES YES</dc:creator>
		<pubDate>Wed, 05 Jan 2011 18:12:03 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=10#comment-3354</guid>
		<description>[...] http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/#more-10 [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/#more-10" rel="nofollow">http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/#more-10</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Running XenApp in a ESX VM -</title>
		<link>http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/comment-page-1/#comment-412</link>
		<dc:creator>Running XenApp in a ESX VM -</dc:creator>
		<pubDate>Tue, 06 Apr 2010 18:29:30 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=10#comment-412</guid>
		<description>[...] be a more severe performance impact. Here a somewhat recent post by Scott Drummonds on that topic: http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/”    Citrix, VMware, Whitepapers [...]</description>
		<content:encoded><![CDATA[<p>[...] be a more severe performance impact. Here a somewhat recent post by Scott Drummonds on that topic: <a href="http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/”" rel="nofollow">http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/”</a>    Citrix, VMware, Whitepapers [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Your Performance Enemy: Host Swapping &#171; Pivot Point</title>
		<link>http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/comment-page-1/#comment-411</link>
		<dc:creator>Your Performance Enemy: Host Swapping &#171; Pivot Point</dc:creator>
		<pubDate>Wed, 23 Dec 2009 18:44:08 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=10#comment-411</guid>
		<description>[...] in challenging discussions on host memory swapping and its impact to performance.  If you read my article on host swapping and the whitepaper it summarized, you know the deleterious effect on performance caused by host [...]</description>
		<content:encoded><![CDATA[<p>[...] in challenging discussions on host memory swapping and its impact to performance.  If you read my article on host swapping and the whitepaper it summarized, you know the deleterious effect on performance caused by host [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fernando</title>
		<link>http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/comment-page-1/#comment-410</link>
		<dc:creator>Fernando</dc:creator>
		<pubDate>Sat, 26 Sep 2009 18:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=10#comment-410</guid>
		<description>What happens is that on 90% of the cases, customer *always* oversize VMs.
Also, it is pure statistics: given a large number of VMs, not all them will need all their memory at the same time (with very, very few exceptions).</description>
		<content:encoded><![CDATA[<p>What happens is that on 90% of the cases, customer *always* oversize VMs.<br />
Also, it is pure statistics: given a large number of VMs, not all them will need all their memory at the same time (with very, very few exceptions).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

