<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>vPivot &#187; pex</title>
	<atom:link href="http://vpivot.com/tag/pex/feed/" rel="self" type="application/rss+xml" />
	<link>http://vpivot.com</link>
	<description>Scott Drummonds on Virtualization</description>
	<lastBuildDate>Wed, 01 Feb 2012 06:46:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Memory Compression</title>
		<link>http://vpivot.com/2010/03/01/memory-compression/</link>
		<comments>http://vpivot.com/2010/03/01/memory-compression/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 01:36:15 +0000</pubDate>
		<dc:creator>drummonds</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[pex]]></category>
		<category><![CDATA[vmworld]]></category>

		<guid isPermaLink="false">http://vpivot.com/?p=313</guid>
		<description><![CDATA[Steve Herrod&#8217;s keynote at Partner Exchange 2010 included a tantalizing slide on an upcoming memory maximization technology: memory compression.  A few of you have already seen the overview of this technology Kit Colbert and Fei Guo previewed it at VMworld 2009.   Today I want to tell you how this upcoming feature will help you pack [...]]]></description>
			<content:encoded><![CDATA[<p>Steve Herrod&#8217;s keynote at Partner Exchange 2010 included a tantalizing slide on an upcoming memory maximization technology: memory compression.  A few of you have already seen the overview of this technology <a href="http://www.vmworld2009.com/docs/DOC-3817">Kit Colbert and Fei Guo previewed it at VMworld 2009</a>.   Today I want to tell you how this upcoming feature will help you pack even more virtual machines onto your existing servers.</p>
<p><span id="more-313"></span>To get the most out of your servers&#8217; memory you have to over-commit it.  Go too far and the host will swap.  This fact is immutable in enterprise memory management.  Because rotating disks have seek times that are <em>six orders of magnitude</em> larger than memory, when your host swaps your applications&#8217; performance suffers catastrophically.  <a href="http://vpivot.com/2009/12/24/solid-state-disks-and-host-swapping/">Solid state drives (SSD) can mitigate the performance cost</a> by reducing swap latency by a couple orders of magnitude.  But SSDs still have delays tens of thousands of times worse than memory.</p>
<p>VMware engineers have been working on a technology that we unofficially call on-demand memory compression (ODMC) or compression cache, depending on who you talk to.  The idea of ODMC is to avoid swapping by compressing a set of target pages to a special region.  We have measured the additional latency&#8211;the compression time&#8211;to be over a hundred times better than rotating disk latencies.  And this will decrease at CPU performance increases.</p>
<p>SSD devices will continue to play an important part in solving the performance problems of extreme memory over-commit because of the great volume of data they can serve at a speed much faster than rotating disks.  But it will be a secondary solution to the faster ODMC, which uses a small dedicated area of system memory.  VMware&#8217;s long-term prioritization for managing the most aggressively over-committed memory looks like this:</p>
<ol>
<li>Do not swap if possible.  We will continue to leverage transparent page sharing and ballooning to make swapping a last resort.</li>
<li>Use ODMC to a predefined cache to decrease memory utilization.*</li>
<li>Swap to persistent memory (SSD) installed locally in the server.**</li>
<li>Swap to the array, which may benefit from installed SSDs.</li>
</ol>
<p>(*) Demonstrated in the lab and coming in a future product.</p>
<p>(**) Part of our vision and not yet demonstrated.</p>
<p>The end goal of this prioritized use of different technologies is the reduction of the performance penalty of swap.  If VMware can reduce the penalty of swap, the virtual machines in extremely over-committed environments will not slow much when they need more memory than the host has available.  When this performance cost of swapping is reduced, you can safely drive your consolidation ratios even higher.</p>
<p>I cannot wait for the general availability of ODMC.  It is another technological accomplishment in a long line of innovation out of our phenomenal engineering organization.  At times I wonder when the last time another operating system software company introduced something really awesome to the industry.  But of course, I am biased.</p>
]]></content:encoded>
			<wfw:commentRss>http://vpivot.com/2010/03/01/memory-compression/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>Windows Guest Defragmentation</title>
		<link>http://vpivot.com/2010/02/12/windows-guest-defragmentation/</link>
		<comments>http://vpivot.com/2010/02/12/windows-guest-defragmentation/#comments</comments>
		<pubDate>Fri, 12 Feb 2010 16:22:55 +0000</pubDate>
		<dc:creator>drummonds</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pex]]></category>
		<category><![CDATA[storage]]></category>
		<category><![CDATA[vmkernel]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://vpivot.com/?p=288</guid>
		<description><![CDATA[Today at VMware Partner Exchange I had a lunchtime discussion with a partner of ours that makes a Windows file system (NTFS) defragmentation tool. He related anecdotes of incredible performance acceleration credited to defragmentation and quoted a few numbers based on his test environment. When he asked me what VMware&#8217;s recommendations were on the subject [...]]]></description>
			<content:encoded><![CDATA[<p>Today at VMware Partner Exchange I had a lunchtime discussion with a partner of ours that makes a Windows file system (NTFS) defragmentation tool.  He related anecdotes of incredible performance acceleration credited to defragmentation and quoted a few numbers based on his test environment.  When he asked me what VMware&#8217;s recommendations were on the subject I remained uncharacteristically silent.  Do we have best practices on this?</p>
<p><span id="more-288"></span>When people ask me about file system fragmentation I explain that fragmentation can come from two sources: the guest file system or VMFS.  In 2009 we included experiments in our <a href="http://www.vmware.com/pdf/vsp_4_thinprov_perf.pdf">thin provisioning white paper</a> that showed that both internal and external fragmentation in VMFS have no significant effect on performance.  As for guest fragmentation, VMware has avoided the business of optimizing native operating systems so there is no extant, official guidance.</p>
<p>More precisely, the large number of mappings from the guest file to the disk make it difficult to know how changes to each can impact the system&#8217;s performance as a whole.  But in talking with this partner I realized that there are two inescapable truths that suggest guest defragmentation is critical in a virtualized environment:</p>
<ol>
<li>Defragmentation can decrease the number of disk commands and the resultant IOPS.</li>
<li>The fewer IOs, the more efficient the virtualization.</li>
</ol>
<p>Guest defrag tools will order each file&#8217;s blocks sequentially in the guest file system.  This will enable the guest to make a few number of calls to larger, contiguous data than had the blocks been separated on the guest file system.  By making fewer calls to larger blocks, the following things happen:</p>
<ul>
<li>The array can leverage its faster sequential access capabilities to improve storage throughput.</li>
<li>The hypervisor handles fewer SCSI messages from the guest resulting in lower overhead.</li>
<li>The smaller number of commands results in fewer outstanding operations in the 32-element HBA queue, which allows more virtual machines to access the storage concurrently.</li>
</ul>
<p>I have not found out how much consolidated workloads have to gain from guest defragmentation.  Nor have I quantified the impact to shared storage of a shift from a larger number of small commands to a smaller number of large commands.  But I am going to work with this partner and see if we can publish some numbers in 2010.</p>
]]></content:encoded>
			<wfw:commentRss>http://vpivot.com/2010/02/12/windows-guest-defragmentation/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Las Vegas Taxi Rates</title>
		<link>http://vpivot.com/2010/02/11/las-vegas-taxi-rates/</link>
		<comments>http://vpivot.com/2010/02/11/las-vegas-taxi-rates/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 21:22:06 +0000</pubDate>
		<dc:creator>drummonds</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[pex]]></category>

		<guid isPermaLink="false">http://vpivot.com/?p=290</guid>
		<description><![CDATA[Let&#8217;s take a break from virtualization and talk about taxi cabs in Las Vegas.  I just got into McCarran airport after a fantastically successful VMware Partner Exchange 2010 and want to ask some of you seasoned veterans of Las Vegas to share your thoughts on a cab problem that I only learned of today. During [...]]]></description>
			<content:encoded><![CDATA[<p>Let&#8217;s take a break from virtualization and talk about taxi cabs in Las Vegas.  I just got into McCarran airport after a fantastically successful VMware Partner Exchange 2010 and want to ask some of you seasoned veterans of Las Vegas to share your thoughts on a cab problem that I only learned of today.</p>
<p><span id="more-290"></span>During my short cab ride from the Mandalay Bay to McCarran (LAS) the driver and I discussed routes and fares to and from the airport.  The route from the airport, favored by taxis that pick you up at LAS, follows the highway, starting on I-215 and then to I-15, at a cost of around $28.  This as opposed to the more direct, airport-bound trip on Paradise, Tropicana and the Boulevard, which takes less time and totals only $11.50.  I asked my driver, &#8220;Why do the taxis to the airport take the second, shorter, cheaper route when the hotel-bound taxis always take the highway?&#8221;  The driver answered simply: &#8220;Airport taxis are f****** crooks.&#8221;</p>
<p>I have spent a little time investigating these two routes on Google maps and they do not seem to be dramatically different in terms of total length.  But clearly the fares differ widely.  I am sure the taxis prefer a larger fare but might there be an innocuous reason for the highway route?  Perhaps the risk of traffic delay is decreased by taking the highway and avoiding the strip?</p>
<p>My driver today seemed certain that greed fuels the decision to take the longer route.  He said that no visitor should ever pay more than $12 for a ride from the airport.  He advised me to refuse payment to the next cabbie that took me for the long ride.  He also said a call to the taxi cab company, which gains from the overcharge, would have no effect.  But a call to the <a href="http://taxi.state.nv.us">taxi cab authority</a> is justified and would result in a $300 fine to the taxi company for the long haul.</p>
<p>Has anyone ever taken the short route from the airport?  Are there any problems with getting taxis to take that route instead of the highway?  Is there a good reason to take the highway instead of surface streets?</p>
]]></content:encoded>
			<wfw:commentRss>http://vpivot.com/2010/02/11/las-vegas-taxi-rates/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
	</channel>
</rss>

