<?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: Performance impact when using VMware snapshots</title>
	<atom:link href="http://www.vmdamentals.com/?feed=rss2&#038;p=332" rel="self" type="application/rss+xml" />
	<link>http://www.vmdamentals.com/?p=332</link>
	<description>VMware Technical Deepdive by Erik Zandboer</description>
	<lastBuildDate>Wed, 18 Aug 2010 20:07:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Erik Zandboer</title>
		<link>http://www.vmdamentals.com/?p=332&#038;cpage=1#comment-183</link>
		<dc:creator>Erik Zandboer</dc:creator>
		<pubDate>Sat, 06 Mar 2010 09:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmdamentals.com/?p=332#comment-183</guid>
		<description>@Jeremy: You can do all that with esxtop, and esxtop can run in batch mode outputting the data you require (-b I think). I used the VI client, the performance tab is also great, and it has a button that lets you save data either as a jpg, or as an Excel file. Especially the Excel option is great for this!</description>
		<content:encoded><![CDATA[<p>@Jeremy: You can do all that with esxtop, and esxtop can run in batch mode outputting the data you require (-b I think). I used the VI client, the performance tab is also great, and it has a button that lets you save data either as a jpg, or as an Excel file. Especially the Excel option is great for this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Benintende</title>
		<link>http://www.vmdamentals.com/?p=332&#038;cpage=1#comment-182</link>
		<dc:creator>Jeremy Benintende</dc:creator>
		<pubDate>Fri, 05 Mar 2010 23:27:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmdamentals.com/?p=332#comment-182</guid>
		<description>Thanks for the write up!  This is really goos stuff and should be linked from VMware communities.

Erik, how did you monitor IO at the ESX level?  esxtop gives you good info, but I&#039;m not sure how to extract the data for my own analysis on my environment.</description>
		<content:encoded><![CDATA[<p>Thanks for the write up!  This is really goos stuff and should be linked from VMware communities.</p>
<p>Erik, how did you monitor IO at the ESX level?  esxtop gives you good info, but I&#8217;m not sure how to extract the data for my own analysis on my environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Zandboer</title>
		<link>http://www.vmdamentals.com/?p=332&#038;cpage=1#comment-171</link>
		<dc:creator>Erik Zandboer</dc:creator>
		<pubDate>Thu, 25 Feb 2010 07:29:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmdamentals.com/?p=332#comment-171</guid>
		<description>@Walle: I know Compellent. They are migrating blocks of data between tiers of storage based on usage. It seems nice, but this is a whole other discussion. I bevlieve compellent can force VMs to stay on faster storage if needed, which is a definite requirement (&quot;the database that comes alive once a month&quot;. With virtualization, ÿou should not care where your VM runs&quot;. That could be true for storage as well, but it is not. You never know what impacts what, I&#039;d always want to know what load impacts what... It is still a nice approach from Compellent. Personally I like Suns 7000 storage even better; they use ZFS for filesystem which performs like crazy from sata alone, but they are using cache and SSDs in a VERY smart way. They&#039;re the only that differ between read and write SSDs (and they have every reason). Be sure to check it out (and no, I do not work for Sun :) )</description>
		<content:encoded><![CDATA[<p>@Walle: I know Compellent. They are migrating blocks of data between tiers of storage based on usage. It seems nice, but this is a whole other discussion. I bevlieve compellent can force VMs to stay on faster storage if needed, which is a definite requirement (&#8220;the database that comes alive once a month&#8221;. With virtualization, ÿou should not care where your VM runs&#8221;. That could be true for storage as well, but it is not. You never know what impacts what, I&#8217;d always want to know what load impacts what&#8230; It is still a nice approach from Compellent. Personally I like Suns 7000 storage even better; they use ZFS for filesystem which performs like crazy from sata alone, but they are using cache and SSDs in a VERY smart way. They&#8217;re the only that differ between read and write SSDs (and they have every reason). Be sure to check it out (and no, I do not work for Sun <img src='http://www.vmdamentals.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  )</p>
]]></content:encoded>
	</item>
</channel>
</rss>
