<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Virtual Performance</title>
    <link>http://communities.vmware.com/blogs/drummonds</link>
    <description>Comment Feed for Virtual Performance on post 'SQL Server Performance Problems Not Due to VMware'</description>
    <pubDate>Thu, 09 Apr 2009 22:55:53 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-04-09T22:55:53Z</dc:date>
    <item>
      <title>RE:&amp;nbsp;SQL Server Performance Problems Not Due to VMware</title>
      <link>http://communities.vmware.com/blogs/drummonds/2009/03/13/sql-server-performance-problems-not-due-to-vmware#comments-11187</link>
      <description>Thanks for the additional information, Brian.  I'd agree with both of your comments, with caveats.  As you can see from above, the SQL priority boost did deliver additional gains to performance.  Our experience with real deployments is that the gain we measured may not translate into the same benefits in production environments.  This being due to the fact that increased priority of the SQL process can cause problems with other processes that could be integral to your architecture's efficiency.&lt;br /&gt;
&lt;br /&gt;
However, I will note that the purpose of this blog was to point out that priority boost could generate up to 5% gain, but this is trivial in the context of performance problems that are halving SQL performance or worse.</description>
      <pubDate>Thu, 09 Apr 2009 22:55:53 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/blogs/drummonds/2009/03/13/sql-server-performance-problems-not-due-to-vmware#comments-11187</guid>
      <dc:date>2009-04-09T22:55:53Z</dc:date>
    </item>
    <item>
      <title>RE:&amp;nbsp;SQL Server Performance Problems Not Due to VMware</title>
      <link>http://communities.vmware.com/blogs/drummonds/2009/03/13/sql-server-performance-problems-not-due-to-vmware#comments-11135</link>
      <description>I'm a big fan of virtualization and we've sought to virtualize where it made sense (and it usually does). However, some of the things you're saying with regards to SQL Server configuration I disagree with. I would in no way say that SQL Server priority boost is a Microsoft best practice for SQL Server configuration. In fact, the truth is it's not. Reference:&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://support.microsoft.com/kb/319942"&gt;http://support.microsoft.com/kb/319942&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
"Based on actual support experience, you do not need to use priority boost for good performance. If you do use priority boost, it can interfere with smooth server functioning under some conditions and you should not use it except under very unusual circumstances. For example, Microsoft Product Support Services might use priority boost when they investigate a performance issue."&lt;br /&gt;
&lt;br /&gt;
And large pages only come into play when you have x64 or ia64 installations with at least 8 GB of RAM (reference: &lt;a class="jive-link-external" href="http://blogs.msdn.com/slavao/archive/2005/02/11/371063.aspx"&gt;http://blogs.msdn.com/slavao/archive/2005/02/11/371063.aspx&lt;/a&gt;). So for smaller installations, that's not available and cannot be suggested as a best practice.</description>
      <pubDate>Thu, 02 Apr 2009 15:46:41 GMT</pubDate>
      <author>KBrianKelley</author>
      <guid>http://communities.vmware.com/blogs/drummonds/2009/03/13/sql-server-performance-problems-not-due-to-vmware#comments-11135</guid>
      <dc:date>2009-04-02T15:46:41Z</dc:date>
    </item>
  </channel>
</rss>

