<?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: PVSCSI and Low IO Workloads</title>
	<atom:link href="http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/feed/" rel="self" type="application/rss+xml" />
	<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/</link>
	<description>Scott Drummonds on Virtualization</description>
	<lastBuildDate>Thu, 26 Aug 2010 18:49:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: More vSphere 4.1 Enhancements &#8211; Welcome Back PVSCSI Driver! &#171; thelowercasew.com</title>
		<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/comment-page-1/#comment-2091</link>
		<dc:creator>More vSphere 4.1 Enhancements &#8211; Welcome Back PVSCSI Driver! &#171; thelowercasew.com</dc:creator>
		<pubDate>Mon, 16 Aug 2010 13:08:07 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=274#comment-2091</guid>
		<description>[...] In a post on his vPivot blog, former VMware performance guru Scott Drummonds echoed the sentiments and stated that this issue would be resolved in a future release of vSphere.  He noted that the PVSCSI driver was only slightly slower than the LSI driver in certain scenarios but acknowledged that it could result in slightly less performance with no efficiency gains. [...]</description>
		<content:encoded><![CDATA[<p>[...] In a post on his vPivot blog, former VMware performance guru Scott Drummonds echoed the sentiments and stated that this issue would be resolved in a future release of vSphere.  He noted that the PVSCSI driver was only slightly slower than the LSI driver in certain scenarios but acknowledged that it could result in slightly less performance with no efficiency gains. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: drummonds</title>
		<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/comment-page-1/#comment-1901</link>
		<dc:creator>drummonds</dc:creator>
		<pubDate>Fri, 23 Jul 2010 05:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=274#comment-1901</guid>
		<description>PVSCSI coalescing has been fixed in ESX 4.1.  VMware has checked in the fix to the code branch that will produce ESX 4.0 U3.  I am not the right person to comment on PVSCI support for SCSI3.</description>
		<content:encoded><![CDATA[<p>PVSCSI coalescing has been fixed in ESX 4.1.  VMware has checked in the fix to the code branch that will produce ESX 4.0 U3.  I am not the right person to comment on PVSCI support for SCSI3.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Bjerregård</title>
		<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/comment-page-1/#comment-1829</link>
		<dc:creator>Erik Bjerregård</dc:creator>
		<pubDate>Wed, 21 Jul 2010 11:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=274#comment-1829</guid>
		<description>Hi, any updates on when PVSCSI will work optimal for low IOPS? Anu new  status on scsi3 support fro PVSCSI?</description>
		<content:encoded><![CDATA[<p>Hi, any updates on when PVSCSI will work optimal for low IOPS? Anu new  status on scsi3 support fro PVSCSI?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware pvSCSI &#8211; When and when not to use it &#124; virtual insanity</title>
		<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/comment-page-1/#comment-751</link>
		<dc:creator>VMware pvSCSI &#8211; When and when not to use it &#124; virtual insanity</dc:creator>
		<pubDate>Thu, 29 Apr 2010 11:31:10 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=274#comment-751</guid>
		<description>[...] I didn’t really understand this and the knowledge base article is lacking any detail on the rational behind the statement.&#160; I reached out to VMware performance engineer Scott Drummonds to see if he had anything he could publish to help clarify the KB article.&#160; Scott was nice enough to research this and posted his findings here. [...]</description>
		<content:encoded><![CDATA[<p>[...] I didn’t really understand this and the knowledge base article is lacking any detail on the rational behind the statement.&#160; I reached out to VMware performance engineer Scott Drummonds to see if he had anything he could publish to help clarify the KB article.&#160; Scott was nice enough to research this and posted his findings here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RTFM Education &#187; Blog Archive &#187; vNews &#8211; Mar, 2010</title>
		<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/comment-page-1/#comment-551</link>
		<dc:creator>RTFM Education &#187; Blog Archive &#187; vNews &#8211; Mar, 2010</dc:creator>
		<pubDate>Thu, 04 Mar 2010 18:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=274#comment-551</guid>
		<description>[...] Citrix release virtual appliances  [...]</description>
		<content:encoded><![CDATA[<p>[...] Citrix release virtual appliances  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Future Imperfect &#187; Blog Archive &#187; PVSCSI or LSI Logic: that is the question</title>
		<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/comment-page-1/#comment-550</link>
		<dc:creator>Future Imperfect &#187; Blog Archive &#187; PVSCSI or LSI Logic: that is the question</dc:creator>
		<pubDate>Fri, 26 Feb 2010 10:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=274#comment-550</guid>
		<description>[...] can read about it at pivot point.   Filed under: I.T, VMWare Comment [...]</description>
		<content:encoded><![CDATA[<p>[...] can read about it at pivot point.   Filed under: I.T, VMWare Comment [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/comment-page-1/#comment-549</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Thu, 25 Feb 2010 18:12:02 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=274#comment-549</guid>
		<description>Exactly!  That is my point in the summary.  If your environment matches the case where pvscsi is slightly worse, by definition you have an application where performance is not important.</description>
		<content:encoded><![CDATA[<p>Exactly!  That is my point in the summary.  If your environment matches the case where pvscsi is slightly worse, by definition you have an application where performance is not important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FP</title>
		<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/comment-page-1/#comment-548</link>
		<dc:creator>FP</dc:creator>
		<pubDate>Thu, 25 Feb 2010 14:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=274#comment-548</guid>
		<description>If I am in a situation where pvscsi is &quot;slightly worse&quot; than the other bus types, it means that I am in an environment with only a small demand for storage performance, right? So why would I care about losing a handlful of ms for my disk access?</description>
		<content:encoded><![CDATA[<p>If I am in a situation where pvscsi is &#8220;slightly worse&#8221; than the other bus types, it means that I am in an environment with only a small demand for storage performance, right? So why would I care about losing a handlful of ms for my disk access?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/comment-page-1/#comment-547</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Tue, 23 Feb 2010 23:05:50 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=274#comment-547</guid>
		<description>Quite the contrary: I recommend that you always use vmxnet.  Use the most recent version available to you.</description>
		<content:encoded><![CDATA[<p>Quite the contrary: I recommend that you always use vmxnet.  Use the most recent version available to you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cw</title>
		<link>http://vpivot.com/2010/02/04/pvscsi-and-low-io-workloads/comment-page-1/#comment-546</link>
		<dc:creator>cw</dc:creator>
		<pubDate>Tue, 23 Feb 2010 22:25:19 +0000</pubDate>
		<guid isPermaLink="false">http://vpivot.com/?p=274#comment-546</guid>
		<description>so you recommend to NOT use VMXNET3 at all?</description>
		<content:encoded><![CDATA[<p>so you recommend to NOT use VMXNET3 at all?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
