<?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>VMware Communities : All Content - Performance &amp; VMmark</title>
    <link>http://communities.vmware.com/community/vmtn/general/performance</link>
    <description>All Content in Performance &amp; VMmark</description>
    <language>en</language>
    <pubDate>Mon, 23 Nov 2009 05:50:41 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-11-23T05:50:41Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>My VMware workstation is very slow!!</title>
      <link>http://communities.vmware.com/message/1423519</link>
      <description>Hi Scissor,&lt;br /&gt;
&lt;br /&gt;
First of all thanks for your help.&lt;br /&gt;
&lt;br /&gt;
1. When you asked for reconfiguring my guest to 1 vCPU, you meant to change the number of processors from 2 to 1, isnt it? (sorry for my lack of knowledge).&lt;br /&gt;
2. I have changed the memory from 3.5 GB to 1 GB as you said, but the software i am running is quite heavy, it has 200GB. How would be the&lt;br /&gt;
maximum amount of RAM I could alocate to my guest? Do you think I would get a better perfmance if I get more memory RAM into this machine?&lt;br /&gt;
3. You are right, I am running the software from an external HDD which there is the software pre-installed.&lt;br /&gt;
&lt;br /&gt;
I would like to say your changes were really helful, the performance has increased a lot, it's not perfect yet, but heaps better than before!&lt;br /&gt;
&lt;br /&gt;
Many thanks mate!</description>
      <pubDate>Mon, 23 Nov 2009 05:50:41 GMT</pubDate>
      <author>pdsouto</author>
      <guid>http://communities.vmware.com/message/1423519</guid>
      <dc:date>2009-11-23T05:50:41Z</dc:date>
      <clearspace:dateToText>11 hours, 1 minute ago</clearspace:dateToText>
      <clearspace:replyCount>16</clearspace:replyCount>
    </item>
    <item>
      <title>Warnings on virtual machine memory usage</title>
      <link>http://communities.vmware.com/message/1423176</link>
      <description>I've installed the latest patch for vSphere 4.&lt;br /&gt;
It was also in the answer from MKGuy, but while waiting on reply's, I did not stop searching &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt; and found the answer maenwhile.</description>
      <pubDate>Sun, 22 Nov 2009 10:20:07 GMT</pubDate>
      <author>walterD</author>
      <guid>http://communities.vmware.com/message/1423176</guid>
      <dc:date>2009-11-22T10:20:07Z</dc:date>
      <clearspace:dateToText>1 day, 6 hours ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>block level and file level transfer</title>
      <link>http://communities.vmware.com/message/1423048</link>
      <description>No worries - hope it is clear now - &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful</description>
      <pubDate>Sat, 21 Nov 2009 23:43:41 GMT</pubDate>
      <author>weinstein5</author>
      <guid>http://communities.vmware.com/message/1423048</guid>
      <dc:date>2009-11-21T23:43:41Z</dc:date>
      <clearspace:dateToText>1 day, 17 hours ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Enable trusted execution</title>
      <link>http://communities.vmware.com/message/1422812</link>
      <description>I have a Dell Optiplex 755, I updated my BIOS settings to Enabled Trusted Execution, VT enabled and virtualization enabled.  Now my machine will boot to a blinking cursor.  I am unable to get back to the BIOS? Is there a way to resolve this?</description>
      <pubDate>Sat, 21 Nov 2009 13:09:43 GMT</pubDate>
      <author>aRandomPerson</author>
      <guid>http://communities.vmware.com/message/1422812</guid>
      <dc:date>2009-11-21T13:09:43Z</dc:date>
      <clearspace:dateToText>2 days, 3 hours ago</clearspace:dateToText>
    </item>
    <item>
      <title>Expected vSwitch/vmxnet network performance?</title>
      <link>http://communities.vmware.com/message/1422376</link>
      <description>&lt;br /&gt;
Hi, I know this is an old post, but hopefully this will help people get a general idea of vSwitch performance. I just did a test in my lab.&lt;br /&gt;
&lt;p /&gt;
You can view my results here under vSwitch Performance Testing.&lt;br /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://www.brandontek.com/"&gt;http://www.brandontek.com/&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">network</category>
      <pubDate>Fri, 20 Nov 2009 18:12:11 GMT</pubDate>
      <author>brandontek</author>
      <guid>http://communities.vmware.com/message/1422376</guid>
      <dc:date>2009-11-20T18:12:11Z</dc:date>
      <clearspace:dateToText>2 days, 22 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>How to fetch historical performance of ESx Server using vmware vi sdk</title>
      <link>http://communities.vmware.com/message/1421914</link>
      <description>Hi,&lt;br /&gt;
&lt;br /&gt;
I was trying the script written by ehayes. Script doesnt throw any output, either it doesnt give any output. Guess the .NET datatable is not getting displayed. Below is the output i get,&lt;br /&gt;
&lt;br /&gt;
Collecting:  INCH-BGD138    mem.usage.average   05/28/2009 00:00   05/28/2009 23:59&lt;br /&gt;
Collecting:  INCH-BGD138    cpu.usage.average   05/28/2009 00:00   05/28/2009 23:59&lt;br /&gt;
&lt;br /&gt;
Any help is appreciated.&lt;br /&gt;
&lt;br /&gt;
Thanks</description>
      <pubDate>Fri, 20 Nov 2009 08:30:34 GMT</pubDate>
      <author>Rajeev S</author>
      <guid>http://communities.vmware.com/message/1421914</guid>
      <dc:date>2009-11-20T08:30:34Z</dc:date>
      <clearspace:dateToText>3 days, 8 hours ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>2 vCPUs Hardware Interupts</title>
      <link>http://communities.vmware.com/message/1421115</link>
      <description>Kichaonline,&lt;br /&gt;
&lt;br /&gt;
I have put in a support request but unfortunatly our support comes through HP.  I don't know if you have anyway of getting them to elevate the SR to you any faster than I can.  The HP SR number is 4606821785.&lt;br /&gt;
&lt;br /&gt;
Wade</description>
      <pubDate>Thu, 19 Nov 2009 14:03:21 GMT</pubDate>
      <author>Wadebum</author>
      <guid>http://communities.vmware.com/message/1421115</guid>
      <dc:date>2009-11-19T14:03:21Z</dc:date>
      <clearspace:dateToText>4 days, 2 hours ago</clearspace:dateToText>
      <clearspace:replyCount>21</clearspace:replyCount>
    </item>
    <item>
      <title>Performance issue using virtualization</title>
      <link>http://communities.vmware.com/message/1420745</link>
      <description>After the kudos, it's embarrassing to admit this, but I did all of this testing with Windows 2003 RTM.  Windows 2003 SP2 has addressed this particular issue.  See &lt;a class="jive-link-external" href="http://technet.microsoft.com/en-us/library/ee407540(WS.10).aspx"&gt;this Microsoft TechNet article&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
After installing SP2, my new timings are 16 seconds for binary translation and only 6 seconds for VT-x (with or without FlexPriority).&lt;br /&gt;
&lt;br /&gt;
To summarize all of these findings: if you are running this kind of a workload on Windows 2003 pre-SP2, you should use binary translation, but on Windows 2003 SP2, you should use hardware virtualization.</description>
      <pubDate>Thu, 19 Nov 2009 00:17:11 GMT</pubDate>
      <author>jmattson</author>
      <guid>http://communities.vmware.com/message/1420745</guid>
      <dc:date>2009-11-19T00:17:11Z</dc:date>
      <clearspace:dateToText>4 days, 16 hours ago</clearspace:dateToText>
      <clearspace:replyCount>19</clearspace:replyCount>
    </item>
    <item>
      <title>SCSI errors on VMs on NFS datastores</title>
      <link>http://communities.vmware.com/message/1419652</link>
      <description>Any luck with this? I am experiencing the exact same issue.  My CentOS images see the problem, but not Windows.  My hardware is a bit different however.  I assumed in my case, that my NFS server too busy, and I need to move some workloads around.</description>
      <pubDate>Tue, 17 Nov 2009 22:53:24 GMT</pubDate>
      <author>wjs</author>
      <guid>http://communities.vmware.com/message/1419652</guid>
      <dc:date>2009-11-17T22:53:24Z</dc:date>
      <clearspace:dateToText>5 days, 17 hours ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>I need to support an ancient application</title>
      <link>http://communities.vmware.com/message/1417081</link>
      <description>Depends on the VMware product.&lt;br /&gt;
In ESX(i) you can easily limit the guests CPU.</description>
      <pubDate>Fri, 13 Nov 2009 23:52:20 GMT</pubDate>
      <author>oreeh</author>
      <guid>http://communities.vmware.com/message/1417081</guid>
      <dc:date>2009-11-13T23:52:20Z</dc:date>
      <clearspace:dateToText>1 week, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>High Ready Times?</title>
      <link>http://communities.vmware.com/message/1416937</link>
      <description>This we thought was very funny when someone was complaining about poor performance, the other 4 4cpu vm's that are all pegged also show a slow down, I hope this makes you giggle.</description>
      <pubDate>Fri, 13 Nov 2009 21:24:37 GMT</pubDate>
      <author>mealan</author>
      <guid>http://communities.vmware.com/message/1416937</guid>
      <dc:date>2009-11-13T21:24:37Z</dc:date>
      <clearspace:dateToText>1 week, 2 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>ESX slow boot at Loading VMKernal IPfc-7.40 (Options")</title>
      <link>http://communities.vmware.com/message/1416159</link>
      <description>&lt;br /&gt;
The card in the VMware HCL and latest driver is lpfc_740 version elx_7.4.0.1. BTW, I would start with SAN zoning. Then, from Emulex BIOS, check whether it's able to scan any LUN. If ok, someting may not right with your ESX.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
vcbMC-1.0.6 Beta&lt;br /&gt;
vcbMC-1.0.7 Lite&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.no-x.org"&gt;http://www.no-x.org&lt;/a&gt;</description>
      <pubDate>Fri, 13 Nov 2009 08:38:18 GMT</pubDate>
      <author>athlon_crazy</author>
      <guid>http://communities.vmware.com/message/1416159</guid>
      <dc:date>2009-11-13T08:38:18Z</dc:date>
      <clearspace:dateToText>1 week, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Disk throughput rates on ESX 3.5 and VSphere</title>
      <link>http://communities.vmware.com/message/1416214</link>
      <description>SUBJECT: POOR PERFORMANCE ABOUT I/O SAN DISK WITH ESX 4&lt;br /&gt;
&lt;p /&gt;
If i'm comparing my performance with IO meter with all benches posted in this communities i'm quite good &lt;img src="!" alt="!" class="jive-image"  /&gt;&lt;br /&gt;
&lt;br /&gt;
But i'm agree 200 % with ANDRO... Performance of ESX compared with a physical server are very bad. The 1 Go file transfer test from local ESX to SAN sounds so good to me than using IOmeter because it's real life ...&lt;br /&gt;
&lt;br /&gt;
2.5 minutes for ESX and 15 seconds from a physical server to write a 3 Go file to the SAN: that's a difference&lt;br /&gt;
&lt;br /&gt;
It's not to be admitted, according to me.&lt;br /&gt;
&lt;br /&gt;
Pls find attached my result bench&lt;br /&gt;
&lt;br /&gt;
Regards to everybody</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">3.5</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vsphere</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">disk_throughput</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">trasfer_rate</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">virtual_file_server</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">file_server</category>
      <pubDate>Fri, 13 Nov 2009 08:37:39 GMT</pubDate>
      <author>newcal</author>
      <guid>http://communities.vmware.com/message/1416214</guid>
      <dc:date>2009-11-13T08:37:39Z</dc:date>
      <clearspace:dateToText>1 week, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>Limit any single process to 25% of cpu</title>
      <link>http://communities.vmware.com/message/1415345</link>
      <description>I've never used it but check these out:&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://deztec.jp/x/05/faireal/BES-index.html"&gt;http://deztec.jp/x/05/faireal/BES-index.html&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://kakku.wordpress.com/2007/10/31/ubuntu-windows-limit-cpu-usage-control-that-bully-ipod-tip/"&gt;http://kakku.wordpress.com/2007/10/31/ubuntu-windows-limit-cpu-usage-control-that-bully-ipod-tip/&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Dennis Procopio - VCP&lt;br /&gt;
&lt;br /&gt;
Please remember to award points for helpful or correct responses.</description>
      <pubDate>Thu, 12 Nov 2009 13:58:57 GMT</pubDate>
      <author>proden20</author>
      <guid>http://communities.vmware.com/message/1415345</guid>
      <dc:date>2009-11-12T13:58:57Z</dc:date>
      <clearspace:dateToText>1 week, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Configuration of Hitachi AMS 2100 SAN Storage to VMWare ESX 3.5 with best performance</title>
      <link>http://communities.vmware.com/message/1414209</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
the easiest way to find out why the perfomance is degraded is to have a look in the performance monitor of the AMS2100 which is in Advanced Settings of the Storage Navigator Modular 2.&lt;br /&gt;
&lt;p /&gt;
Then you can analyse where is the problem. High write pending rates are poision for good I/O rates. High usage of single disks or raid groups as well.&lt;br /&gt;
&lt;p /&gt;
 Why did you use LUSE LUNs? This is just an advantage when you pick a LUN out of different RAID groups.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Regards&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Sebastian &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">bestpractice</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx3.5</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance_issues</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance_testing</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">san</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">sata</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">storage</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">analysis</category>
      <pubDate>Wed, 11 Nov 2009 11:21:52 GMT</pubDate>
      <author>Seb. Bauer</author>
      <guid>http://communities.vmware.com/message/1414209</guid>
      <dc:date>2009-11-11T11:21:52Z</dc:date>
      <clearspace:dateToText>1 week, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Very slow startup HP 6730b notebook</title>
      <link>http://communities.vmware.com/message/1410886</link>
      <description>&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.mcgeown.co.uk/BlogEngine/post/2009/02/18/VMWare-Server-The-VMware-Host-Agent-service-terminated-with-service-specific-error-4294967295-%280xFFFFFFFF%29.aspx"&gt;http://www.mcgeown.co.uk/BlogEngine/post/2009/02/18/VMWare-Server-The-VMware-Host-Agent-service-terminated-with-service-specific-error-4294967295-%280xFFFFFFFF%29.aspx&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
 I found this blog which refers to a corrupt datastores.xml file.&lt;br /&gt;
&lt;p /&gt;
 However, I do not have this file in the location specified?  I'm a little puzzled by this?  I also had the error in my windows event logs:&lt;br /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://www.mcgeown.co.uk/BlogEngine/post/2009/02/18/VMWare-Server-The-VMware-Host-Agent-service-terminated-with-service-specific-error-4294967295-%280xFFFFFFFF%29.aspx"&gt;VMWare Server: The VMware Host Agent service terminated with service-specific error 4294967295 (0xFFFFFFFF).&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
Perhaps this will help others too?&lt;br /&gt;
&lt;p /&gt;
Here's what the post says:&lt;br /&gt;
&lt;br /&gt;
&lt;h1&gt;&lt;a class="jive-link-external" href="http://www.mcgeown.co.uk/BlogEngine/post/2009/02/18/VMWare-Server-The-VMware-Host-Agent-service-terminated-with-service-specific-error-4294967295-%280xFFFFFFFF%29.aspx"&gt;VMWare Server: The VMware Host Agent service terminated with service-specific error 4294967295 (0xFFFFFFFF).&lt;/a&gt;&lt;/h1&gt;
&lt;br /&gt;
Having just rebooted my laptop, I clicked on the link to open VMWare Infrastructure Web Access in the my browser and was slightly puzzled by the "page cannot be displayed" error. I figured it was probably the VMWare Server Web Access service not starting for some reason, so I opened services.msc and checked it out. The Web Access service was actually running, but the Host Agent service was not, so I tried to start it - it failed. Dutifully opening Event Viewer for some more information I found the error: &lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;&lt;i&gt;The VMware Host Agent service terminated with service-specific error 4294967295 (0xFFFFFFFF).&lt;/i&gt;&lt;/blockquote&gt;
&lt;br /&gt;
Great. Thanks for the elaboration. Time to check the VMWare logs, (c:\ProgramData\VMWare\VMWare Server\) - the most recent of which contained the following entry: &lt;br /&gt;
&lt;br /&gt;
&lt;blockquote&gt;&lt;i&gt;&lt;strike&gt;2009-02-18 10:55:27.908 'App' 4408 info&lt;/strike&gt; Trying hostsvc&lt;/i&gt; &lt;br clear="all" /&gt; +	&lt;strike&gt;2009-02-18 10:55:27.948 'App' 4408 panic&lt;/strike&gt; error: not well-formed (invalid token)+ &lt;br clear="all" /&gt; +	&lt;strike&gt;2009-02-18 10:55:27.948 'App' 4408 panic&lt;/strike&gt; backtrace:(backtraces not supported)+ &lt;br clear="all" /&gt; +	&lt;strike&gt;2009-02-18 10:55:27.948 'App' 4408 info&lt;/strike&gt; Win32 service stopped+&lt;/blockquote&gt;
&lt;br /&gt;
 A bit of Googling pointed me in the right direction, "not well-formed" refers to the XML config files which are stored in c:\ProgramData\VMWare\VMWare Server\hostd, after that it was just a case of opening each one in turn until I found the malformed one. I backed it up and replaced it with a default version, and lo and behold, my services started! &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
fantastic stuff.. this plagued me as well.. turned out to be the datastores.xml fine was corrupted/empty. There was however another version of the file called datastores.xml.default. so i just renamed that to be datastores.xml and started the VMware Host Agent. Perfect, Thanks!!&lt;br /&gt;
&lt;p /&gt;
best &lt;br /&gt;
&lt;p /&gt;
Monday 30 March 2009 16:02&lt;br /&gt;
&lt;p /&gt;
had the same problem, corrupt datastores.xml file, moved it out and started the VMware Host Agent. &lt;br /&gt;
Worked a charm....Thanks!&lt;br /&gt;
&lt;p /&gt;
mack &lt;br /&gt;
&lt;p /&gt;
Thursday 11 June 2009 10:16&lt;br /&gt;
&lt;p /&gt;
Thanks to all of you for taking the time out to share this with all of us! This fixed my problem within minutes!</description>
      <pubDate>Fri, 06 Nov 2009 14:52:35 GMT</pubDate>
      <author>atom88</author>
      <guid>http://communities.vmware.com/message/1410886</guid>
      <dc:date>2009-11-06T14:52:35Z</dc:date>
      <clearspace:dateToText>2 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>12</clearspace:replyCount>
    </item>
    <item>
      <title>VM object in perfmon not listed?</title>
      <link>http://communities.vmware.com/message/1409703</link>
      <description>Close and re-open Perfmon (the VM objects sometimes appear, sometimes don't), or try re-installing VMware Tools. &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt;&lt;br /&gt;
&lt;br /&gt;
Scott.&lt;br /&gt;
&lt;hr /&gt;
Blog: &lt;a class="jive-link-external" href="http://vmwaretraining.blogspot.com/"&gt;http://vmwaretraining.blogspot.com&lt;/a&gt;&lt;br /&gt;
Web: &lt;a class="jive-link-external" href="http://www.thinkvirtually.co.uk/"&gt;http://www.thinkvirtually.co.uk&lt;/a&gt;&lt;br /&gt;
Twitter: &lt;a class="jive-link-external" href="http://twitter.com/vmtraining"&gt;http://twitter.com/vmtraining&lt;/a&gt; and &lt;a class="jive-link-external" href="http://twitter.com/thinkvirtually"&gt;http://twitter.com/thinkvirtually&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">perfmon</category>
      <pubDate>Thu, 05 Nov 2009 13:46:06 GMT</pubDate>
      <author>scott28tt</author>
      <guid>http://communities.vmware.com/message/1409703</guid>
      <dc:date>2009-11-05T13:46:06Z</dc:date>
      <clearspace:dateToText>2 weeks, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Virtual Desktop Performance issues - ESX 3.5 VM View</title>
      <link>http://communities.vmware.com/message/1408796</link>
      <description>&lt;br /&gt;
Sorry, wasn't sure what category to submit this under.&lt;br /&gt;
&lt;p /&gt;
 I have a small environment running 1 VM server and 5 VM Desktops. Performance on the Desktop side is the issue.&lt;br /&gt;
&lt;p /&gt;
Server Hardware:&lt;br /&gt;
1 - Dell 2950 / 2-Quad 2.8ghz Proc / 16gb RAM / 1.2TB of local storage - 15k RPM HD's / 2 - Dual NIC's (1 NIC = 2 VM Desktops, 1 NIC = 3 VM Desktops and 2 NIC = Server)&lt;br /&gt;
&lt;p /&gt;
Software:&lt;br /&gt;
Server -&amp;gt; SBS 2008&lt;br /&gt;
PC's -&amp;gt; Windows XP Pro SP3 - Office 2003, ERP Application, File Maker, Adobe and WinZip&lt;br /&gt;
&lt;p /&gt;
Virtual Hardware:&lt;br /&gt;
1 2.8ghz Proc / 1gb RAM / 25gb C:\ drive (15gb free)&lt;br /&gt;
&lt;p /&gt;
Physical Hardware used for Virtual PC's:&lt;br /&gt;
Dell Dimension 2400 -&amp;gt; 2.4ghz Single Proc, 512mb or 768mb RAM, 100mb NIC&lt;br /&gt;
&lt;p /&gt;
Issues:&lt;br /&gt;
VM users are seeing slowness issues when attaching documents to emails in Outlook. &lt;br /&gt;
Refresh is slow when changing from one email to another.&lt;br /&gt;
Working in one application and then toggling to another hangs the desktop for a bit.&lt;br /&gt;
Generally speaking applications seem to be slow. &lt;br /&gt;
&lt;p /&gt;
What is my bottleneck? Is this typical or is there a config change that can be made to resolve the issues?&lt;br /&gt;
&lt;p /&gt;
Help would be greatly appreciated.&lt;br /&gt;
&lt;p /&gt;
Marc&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Wed, 04 Nov 2009 17:26:43 GMT</pubDate>
      <author>ciberweb</author>
      <guid>http://communities.vmware.com/message/1408796</guid>
      <dc:date>2009-11-04T17:26:43Z</dc:date>
      <clearspace:dateToText>2 weeks, 4 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Advanced Networking Performance Options</title>
      <link>http://communities.vmware.com/docs/DOC-10892</link>
      <description>Some of the advanced networking options available in vSphere 4.0 are reviewed in this paper. Many of these options control trade-offs between latency, throughput, CPU utilization, and reliability (e.g., dropped packets). It is not possible to optimize all of these at the same time, so option defaults are chosen to be suitable for the vast majority of applications. These options are provided to meet the stricter requirements of other applications. Advanced options often have subtle side effects, or merely move an issue from one area to another. Therefore it is recommended that VMware Support be engaged before changing such options, especially for production machines.&lt;br /&gt;
&lt;br /&gt;
There are over 100 options that can be set under Configuration &amp;rarr; Advanced Settings &amp;rarr; Net. Of these, the ones listed below are most likely to be useful for tuning networking performance. Many of the others are for internal testing or enable unreliable features.&lt;br /&gt;
&lt;br /&gt;
All of the options listed here take integer values. For the &amp;ldquo;Boolean&amp;rdquo; ones only the default value is shown: 0 for &amp;ldquo;false&amp;rdquo;, and 1 for &amp;ldquo;true&amp;rdquo;. Other parameters are shown with their default, minimum, and maximum values.&lt;br /&gt;
&lt;br /&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;Parameter Name&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;(Default, Minimum, Maximum)&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Description&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MaxPortRxQueueLen&lt;/td&gt;
&lt;td&gt;(80, 1, 500)&lt;/td&gt;
&lt;td&gt;Maximum length of the Rx queue for virtual ports whose clients support queueing. Possibly should be increased if Rx packet drops are seen in the port connected to a VM. Relevant only for e1000 vNICs used with Fault Tolerance (FT) and VLANs.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MaxNetifTxQueueLen&lt;/td&gt;
&lt;td&gt;(500, 1, 1000)&lt;/td&gt;
&lt;td&gt;Maximum length of the Tx queue for the physical NICs. Increase if Tx packet drops are seen in uplink port to the pNIC.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GuestTxCopyBreak&lt;/td&gt;
&lt;td&gt;(64, 60, 4294967295)&lt;/td&gt;
&lt;td&gt;Packet header transmits smaller than this in bytes will be copied rather than mapped. More security and functionality than performance implications.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VmxnetTxCopySize&lt;/td&gt;
&lt;td&gt;(256, 0, 4294967295)&lt;/td&gt;
&lt;td&gt;Transmits smaller than this in bytes will be copied rather than mapped. Copying costs CPU but puts lets pressure on the Tx queue and doesn&amp;rsquo;t require completion.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VmxnetWinUDPTxFullCopy&lt;/td&gt;
&lt;td&gt;(1)&lt;/td&gt;
&lt;td&gt;Enable full copy of Windows vmxnet UDP Tx packets. Might disable to save CPU, especially for jumbo frames, at the cost of risking more packet drops.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;NetTxDontClusterSize&lt;/td&gt;
&lt;td&gt;(0, 0, 8192)&lt;/td&gt;
&lt;td&gt;Tx packet size (in bytes) smaller than this are transmitted immediately (coalescing options are over-ruled for these packets). Used to ensure good latency for small packets.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CoalesceTxTimeout&lt;/td&gt;
&lt;td&gt;(4000, 1, 4294967295)&lt;/td&gt;
&lt;td&gt;The coalesce timeout in micro-seconds, or effectively the maximum latency without transmitting. Smaller values can reduce the packet latency at the cost of CPU. Risky to go below 1000.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CoalesceDefaultOn&lt;/td&gt;
&lt;td&gt;(1)&lt;/td&gt;
&lt;td&gt;Enable dynamic coalescing. Disable to test if issues are related to coalescing.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CoalesceHandlerPcpu&lt;/td&gt;
&lt;td&gt;(1, 0, 128)&lt;/td&gt;
&lt;td&gt;pCPU that coalesce timeout handler runs on. May be important to set this if VM CPU pinning is used.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CoalesceTxQDepthCap&lt;/td&gt;
&lt;td&gt;(40, 0, 80)&lt;/td&gt;
&lt;td&gt;Maximum number of &amp;ldquo;normalized&amp;rdquo; Tx packets to coalesce. Reduce if Tx coalescing appears to be too aggressive.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CoalesceRxQDepthCap&lt;/td&gt;
&lt;td&gt;(40, 0, 80)&lt;/td&gt;
&lt;td&gt;Maximum number of &amp;ldquo;normalized&amp;rdquo; Rx packets to coalesce. Reduce if Rx coalescing appears to be too aggressive.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;vmxnetThroughputWeight&lt;/td&gt;
&lt;td&gt;(0, 0, 255)&lt;/td&gt;
&lt;td&gt;How far to favor Tx throughput for vmxnet 2 &amp;#38; 3. &amp;ldquo;0&amp;rdquo; is dynamic, otherwise this is a weight where a lower value favors latency and a higher value favors throughput.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;TcpipHeapSize&lt;/td&gt;
&lt;td&gt;(24, 24, 120)&lt;/td&gt;
&lt;td&gt;Initial size of the TCP/IP module heap in megabytes. May need to increase if there are many vmkernel connections (NFS, iSCSI, etc.).&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;TcpipDefLROMaxLength&lt;/td&gt;
&lt;td&gt;(16000, 1, 65535)&lt;/td&gt;
&lt;td&gt;Maximum length for the LRO aggregated packet for vmkernel connections. Increasing this reduces the number of acknowledgments, which improves efficiency but may increase latency.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;E1000TxZeroCopy&lt;/td&gt;
&lt;td&gt;(0)&lt;/td&gt;
&lt;td&gt;If disabled copy UDP or non-TSO Tx packets for e1000.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;E1000TxTsoZeroCopy&lt;/td&gt;
&lt;td&gt;(1)&lt;/td&gt;
&lt;td&gt;If enabled do not copy TSO Tx packets for e1000.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;E1000IntrCoalesce&lt;/td&gt;
&lt;td&gt;(1)&lt;/td&gt;
&lt;td&gt;Enable interrupt coalescing for e1000. Disabling can improve latency at the expense of CPU.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MaxPktRxListQueue&lt;/td&gt;
&lt;td&gt;(3500, 0, 200000)&lt;/td&gt;
&lt;td&gt;Maximum number of packets queued in vmkernel. Increasing this can reduce the number of dropped packets but at the cost of increased vmkernel memory and queuing latency.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vmxnet3RSSHashCache&lt;/td&gt;
&lt;td&gt;(1)&lt;/td&gt;
&lt;td&gt;Enable RSS hash cache for vmxnet3 in Windows guests.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VmklnxLROEnabled&lt;/td&gt;
&lt;td&gt;(0)&lt;/td&gt;
&lt;td&gt;Enable large packets for recent Linux guests with vmxnet 2 &amp;#38; 3. Most likely to benefit hosts with small number of VMs with few sessions each, where each session has a heavy Rx load (more than 1 MB/sec). This is an experimental feature and has not been tested extensively.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VmklnxLROMaxAggr&lt;/td&gt;
&lt;td&gt;(6, 0, 24)&lt;/td&gt;
&lt;td&gt;Maximum aggregation count in number of packets for vmklinux LRO.&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">kernel</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">network</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">virtualcenter</category>
      <pubDate>Wed, 14 Oct 2009 16:58:33 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/docs/DOC-10892</guid>
      <dc:date>2009-10-14T16:58:33Z</dc:date>
      <clearspace:dateToText>2 weeks, 5 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>creating vm pc's?</title>
      <link>http://communities.vmware.com/message/1407439</link>
      <description>&lt;br /&gt;
VSphere 4.0, VCenter 4.0, ESX hosts = 9 all using HA and DRS on one Cluster&lt;br /&gt;
&lt;p /&gt;
My question is, Is it possible to  deploy a PC workstation using LANdesk on the VIC?&lt;br /&gt;
&lt;p /&gt;
Can we use a PXE boot?</description>
      <pubDate>Tue, 03 Nov 2009 16:28:37 GMT</pubDate>
      <author>KNardi</author>
      <guid>http://communities.vmware.com/message/1407439</guid>
      <dc:date>2009-11-03T16:28:37Z</dc:date>
      <clearspace:dateToText>2 weeks, 6 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>IOMeter testing within the Service Console</title>
      <link>http://communities.vmware.com/message/1407082</link>
      <description>As a previous poster also mentioned, running IOmeter or any other sort of benchmark from inside of the service console will not give you any useful data. Firstly, the SC is actually a virtual machine and has to go through the vmkernel to perform disk IO just like any other VM, and secondly the SC is intentionally limited in how much I/O it is allowed to generate. So if you were to run IOmeter you would see that your benchmark runs from inside the SC was much slower than what you'd see from a regular guest VM.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">iometer</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">iscsi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx3.5</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">san</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">best</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">practice</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">benchmarking</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vmfs</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">install</category>
      <pubDate>Tue, 03 Nov 2009 11:30:27 GMT</pubDate>
      <author>oschistad</author>
      <guid>http://communities.vmware.com/message/1407082</guid>
      <dc:date>2009-11-03T11:30:27Z</dc:date>
      <clearspace:dateToText>2 weeks, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Disk performance strangeness (Guest OS slow, ESX storage blazing fast)</title>
      <link>http://communities.vmware.com/message/1406962</link>
      <description>&lt;br /&gt;
Well, in our case it's actually the buslogic driver which gives us good performance while the lsilogic parallell scsi runs like molasses.</description>
      <pubDate>Tue, 03 Nov 2009 09:00:47 GMT</pubDate>
      <author>oschistad</author>
      <guid>http://communities.vmware.com/message/1406962</guid>
      <dc:date>2009-11-03T09:00:47Z</dc:date>
      <clearspace:dateToText>2 weeks, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>AMD Opteron 2435 2.60 GHz Six Core VS Quad Core AMD Opteron(tm) 8384; 2.7GHz</title>
      <link>http://communities.vmware.com/message/1406590</link>
      <description>&lt;br /&gt;
Dear All,&lt;br /&gt;
&lt;p /&gt;
I'm new in the vmware community.&lt;br /&gt;
&lt;p /&gt;
I'm using vmware Enterprise 3.5 since 3 years.&lt;br /&gt;
&lt;p /&gt;
 I need to change two of my vmware hosts and I would like to know which benchmark score this two different machines have.&lt;br /&gt;
&lt;p /&gt;
both machine are dual socket equiped.&lt;br /&gt;
&lt;p /&gt;
Thanks a lot for your help.</description>
      <pubDate>Mon, 02 Nov 2009 21:31:57 GMT</pubDate>
      <author>fanzalone</author>
      <guid>http://communities.vmware.com/message/1406590</guid>
      <dc:date>2009-11-02T21:31:57Z</dc:date>
      <clearspace:dateToText>2 weeks, 6 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Memory Reporting: who do I trust - vCenter or Windows PerfMon?</title>
      <link>http://communities.vmware.com/message/1404977</link>
      <description>The guest will have better visibility to how active it's memory usage is.  Guest active memory is an approximation by ESX(i) of what it thinks the guest is activitely using for memory.   It can take time to catch up to the guest OS and shouldn't be a concern unless the number begins to approach the memory assigned to the guest.   As an application requests and then frees memory,  the guest OS will track this accurately,  but the management of allocated and freed memory is not passed to the hypervisor level.&lt;br /&gt;
&lt;br /&gt;
In regards to the guests using 100% memory,   it believes that it has physical memory and thus will allocate memory as it sees fit.   Should it approach it's limit it will begin to swap to disk just as guest OS would on a physical host.  What is different from a physical host is that ESX(i) will use transparent page sharing, ballooning and if necessary swapping to provide memory to all the guests running on it.&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Dave &lt;br /&gt;
VMware Communities User Moderator &lt;br /&gt;
&lt;br /&gt;
New book in town - vSphere Quick Start Guide  -&lt;a class="jive-link-external" href="http://www.yellow-bricks.com/2009/08/12/new-book-in-town-vsphere-quick-start-guide/"&gt;http://www.yellow-bricks.com/2009/08/12/new-book-in-town-vsphere-quick-start-guide/&lt;/a&gt;.&lt;br /&gt;
Do you have a system or PCI card working with VMDirectPath?  Submit your specs to the Unofficial VMDirectPath HCL - &lt;a class="jive-link-external" href="http://www.vm-help.com/forum/viewforum.php?f=21"&gt;http://www.vm-help.com/forum/viewforum.php?f=21&lt;/a&gt;.</description>
      <pubDate>Sat, 31 Oct 2009 10:05:00 GMT</pubDate>
      <author>Dave.Mishchenko</author>
      <guid>http://communities.vmware.com/message/1404977</guid>
      <dc:date>2009-10-31T10:05:00Z</dc:date>
      <clearspace:dateToText>3 weeks, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>What VMware product to use? Your dream setup high-powered personal workstation...</title>
      <link>http://communities.vmware.com/message/1404650</link>
      <description>&lt;br /&gt;
Hello All,&lt;br /&gt;
&lt;p /&gt;
If you want to run multiple guest O/S's for your personal workstation, and want the absolute highest possible desktop performance ever (including graphics performance) and you had a big beefy host with plenty of CPU &amp;#38; RAM to put it on, would you run vSphere, ESXi, or Workstation 7 on it (all cost considerations aside) and if you chose Workstation, what base O/S would you use assuming you want maximum RAM available to guests?&lt;br /&gt;
&lt;p /&gt;
Thanks!&lt;br /&gt;
&lt;p /&gt;
Eric</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">high_performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">workstation</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">best_performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">dream_system</category>
      <pubDate>Fri, 30 Oct 2009 20:20:47 GMT</pubDate>
      <author>EricBryant</author>
      <guid>http://communities.vmware.com/message/1404650</guid>
      <dc:date>2009-10-30T20:20:47Z</dc:date>
      <clearspace:dateToText>3 weeks, 2 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>VM suddenly running VERY slow</title>
      <link>http://communities.vmware.com/message/1404244</link>
      <description>&lt;br /&gt;
They were identical to what they are now. It's very odd. It was almost as if the server itself was ok, it was just the Windows GUI that taking was taking enternity to respond.&lt;br /&gt;
&lt;p /&gt;
Either way, the move has obviously kicked it back into life. Thanks for your help.</description>
      <pubDate>Fri, 30 Oct 2009 14:34:41 GMT</pubDate>
      <author>mattstewartcsd</author>
      <guid>http://communities.vmware.com/message/1404244</guid>
      <dc:date>2009-10-30T14:34:41Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>vSphere vcpu scheduling imbalance</title>
      <link>http://communities.vmware.com/message/1403306</link>
      <description>My group has been doing some testing comparing virtual to bare-metal performance with a particularly high-compute utilizing application.&lt;br /&gt;
&lt;br /&gt;
Platform: Intel E5540 (Nehalem) quad-core, dual-socket. 48GB of 1066MHz memory (properly balanced)&lt;br /&gt;
&lt;br /&gt;
OS/guest OS: RHEL 4.7 (for both bare-metal and virtual configs)&lt;br /&gt;
Configuration: Hyper-threading off for both esx and bare-metal. Numa enabled and verified on both ESX and RHEL 4.7 (bare-metal)&lt;br /&gt;
ESX version: 4.0u0  build 164009&lt;br /&gt;
ESX host power.CpuPolicy is set to "static"&lt;br /&gt;
&lt;br /&gt;
The application is a single-threaded modeling/simulation type program. It is not I/O intensive at all and basically each job generates a load average contribution of 1 (i.e. it pegs a cpu for each job). What we have been doing is running 1,2,4, and 8 simultaneous jobs and comparing the virtual to bare-metal physical performance with different combinations of VM vcpu counts (1,2,4 vcpu). Don't know a lot of details about the application other than when scaling from 1 to 8 jobs on bare-metal, the performance of any one job degrades somewhat so it seems to be memory constrained (not sure if the is sensitive to last level cache size or raw RAM performance). The "model" size itself for each job is 1.5GB.&lt;br /&gt;
&lt;br /&gt;
The observation is that when simultaneously running 2 and 4 of these applications, each in its own 2vcpu virtual (so 2 and 4 virtuals respectively but all running on one 2-socket physical). More often that not for the 2 job case, we will see the worlds representing these active vcpus both running on 1 socket (with the other socket basically idle). For the 4 job case (though not as frequently), we have seen the load split 3/1 across the 2 sockets. When we run 8 jobs we get an even distribution of active vcpu worlds across the 2 sockets (4 on each).&lt;br /&gt;
&lt;br /&gt;
The question is: Why is it that when there are 2 active vcpus does ESX schedule these vcpus on one socket more often than not. Same thing for 4 active vcpus, lopsided scheduling 3/1, though not as frequently. The hypothesis is that this behavior is related to some power management function of the scheduler (i.e. it would rather load up one socket more fully so that the cores on the other socket have a chance to be freq scaled down or in the halted state and therefore save power).&lt;br /&gt;
&lt;br /&gt;
Ordinarily for an application that is not sensitive to memory performance or last level cache size this might not be an issue but for our application it apparently is sensitive the load being spread across sockets.&lt;br /&gt;
&lt;br /&gt;
We can workaround this lopsided scheduling by using affinity rules to pin virtuals to sockets and manually force the load to be spread but we were hoping for some way to get it to balance the load without using affinity rules. Note that our hosts are running with power.CpuPolicy static.&lt;br /&gt;
&lt;br /&gt;
Any ideas?&lt;br /&gt;
&lt;br /&gt;
Message was edited by: ltbraswell changed subject to remove the reference to version 4</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">scheduling</category>
      <pubDate>Thu, 29 Oct 2009 19:16:11 GMT</pubDate>
      <author>ltbraswell</author>
      <guid>http://communities.vmware.com/message/1403306</guid>
      <dc:date>2009-10-29T19:16:11Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>ESXi 4.0 shows incorrect memory usage at host level</title>
      <link>http://communities.vmware.com/message/1403140</link>
      <description>&lt;br /&gt;
Hey,&lt;br /&gt;
&lt;p /&gt;
 I've installed the Nehlem patch on my ESXi 4.0 boxes (current build #193498).  The individual guest VM's now report their Active memory correctly, and Memory Usage is also correct, however at the host level it now appears that ESX is reporting Memory Usage (%) based on Consumed memory instead of Active Memory.  &lt;br /&gt;
&lt;p /&gt;
 Has anyone else encountered this?&lt;br /&gt;
&lt;p /&gt;
Thanks,&lt;br /&gt;
&lt;p /&gt;
Garrick</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">memory</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxi4</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">memory_usage</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">active_memory</category>
      <pubDate>Thu, 29 Oct 2009 17:33:56 GMT</pubDate>
      <author>dasbacgl</author>
      <guid>http://communities.vmware.com/message/1403140</guid>
      <dc:date>2009-10-29T17:33:56Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>When to add additional memory to VM?</title>
      <link>http://communities.vmware.com/message/1402659</link>
      <description>I mean that oveall amount of your RAM is 4 Gb and you config VM to use 2 Gb, your system may run slow.&lt;br /&gt;
&lt;br /&gt;
StarWind Software R&amp;#38;D&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.starwindsoftware.com"&gt;http://www.starwindsoftware.com&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">killr</category>
      <pubDate>Thu, 29 Oct 2009 11:31:38 GMT</pubDate>
      <author>TobiasKracht</author>
      <guid>http://communities.vmware.com/message/1402659</guid>
      <dc:date>2009-10-29T11:31:38Z</dc:date>
      <clearspace:dateToText>3 weeks, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Performance</title>
      <link>http://communities.vmware.com/message/1402389</link>
      <description>HI,&lt;br /&gt;
&lt;br /&gt;
I installed ESX3.5i and created 2VM's , booting of the VM's are very slow &lt;br /&gt;
&lt;br /&gt;
1. HP blade 8.GBRam, 2.6CPU assigned 3.5GB for VM still it is taking 16min's to boot to window's &lt;br /&gt;
configured with windows2003 with SP2,Etrust antivirus,with updates and windows latest Update &lt;br /&gt;
&lt;br /&gt;
2. When ever we take base Server Restart NTP service is getting Down.&lt;br /&gt;
&lt;br /&gt;
3. I am facing in VM's Network problem using Netbios copy it is taking around 14mins has taken 64mb file &lt;br /&gt;
&lt;br /&gt;
Kindly let me know Anyone has faced this issue.</description>
      <pubDate>Thu, 29 Oct 2009 05:02:58 GMT</pubDate>
      <author>nellore</author>
      <guid>http://communities.vmware.com/message/1402389</guid>
      <dc:date>2009-10-29T05:02:58Z</dc:date>
      <clearspace:dateToText>3 weeks, 4 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Anyone familiar with STPNavigator tool</title>
      <link>http://communities.vmware.com/message/1402255</link>
      <description>Sorry, I'm not familiar with this tool at all.  But this is the community (or possibly the vSphere storage community) where knowledgeable people are.&lt;br /&gt;
&lt;br /&gt;
Regards, Robert</description>
      <pubDate>Thu, 29 Oct 2009 01:03:40 GMT</pubDate>
      <author>RDellimmagine</author>
      <guid>http://communities.vmware.com/message/1402255</guid>
      <dc:date>2009-10-29T01:03:40Z</dc:date>
      <clearspace:dateToText>3 weeks, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Windows 2008R2 Terminal server - very bad performance</title>
      <link>http://communities.vmware.com/message/1402050</link>
      <description>Windows 2008 R2 is still not supported on ESX 4.&lt;br /&gt;
&lt;p /&gt;
&lt;a class="jive-link-blog" href="http://communities.vmware.com/blogs/aandriolli" title="Direto do dia-a-dia prático para quem virtualiza por profissão. IMPORTANTE: as opiniões aqui expressas são de cunho particular e de forma alguma devem ser atribuidas à VMware, Inc."&gt;VMs Made in Brazil&lt;/a&gt;&lt;br /&gt;
PS: por favor considere dar pontos a este ou qualquer outro post caso lhe seja &amp;uacute;til.</description>
      <pubDate>Wed, 28 Oct 2009 21:19:54 GMT</pubDate>
      <author>aandriolli</author>
      <guid>http://communities.vmware.com/message/1402050</guid>
      <dc:date>2009-10-28T21:19:54Z</dc:date>
      <clearspace:dateToText>3 weeks, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Keyboard and Screens slow to respond</title>
      <link>http://communities.vmware.com/message/1402012</link>
      <description>Try following recommendations at&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://virtrix.blogspot.com/2007/03/vmware-best-practices-for-deploying.html"&gt;http://virtrix.blogspot.com/2007/03/vmware-best-practices-for-deploying.html&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://viops.vmware.com/home/docs/DOC-1226"&gt;http://viops.vmware.com/home/docs/DOC-1226&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Also, for Terminal Services VMs you might consider installing the VM from zero instead of P2V:&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/thread/193845"&gt;http://communities.vmware.com/thread/193845&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br&gt;&lt;br&gt;&lt;a class="jive-link-external" href="http://communities.vmware.com/blogs/aandriolli"&gt;VMs Made in Brazil&lt;/a&gt;&lt;br /&gt;
PS: por favor considere dar pontos a este ou qualquer outro post caso lhe seja útil.</description>
      <pubDate>Wed, 28 Oct 2009 21:00:02 GMT</pubDate>
      <author>aandriolli</author>
      <guid>http://communities.vmware.com/message/1402012</guid>
      <dc:date>2009-10-28T21:00:02Z</dc:date>
      <clearspace:dateToText>3 weeks, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Capacity Question</title>
      <link>http://communities.vmware.com/message/1401294</link>
      <description>Hello.&lt;br /&gt;
&lt;br /&gt;
Can you describe more about the hardware and software you plan to use?  VMware Server on a 3 disk RAID 5 array will have very different scalability in comparison to ESX with shared storage.  If you just need general ideas, check out the &lt;a class="jive-link-external" href="http://vmware.com/go/calculator"&gt;VMware Calculator&lt;/a&gt; or the &lt;a class="jive-link-external" href="http://g3w1656g-vip.houston.hp.com/SB/VMware/UI/index.aspx"&gt;HP VMware Solution Sizer&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
Good Luck!</description>
      <pubDate>Wed, 28 Oct 2009 12:12:12 GMT</pubDate>
      <author>vmroyale</author>
      <guid>http://communities.vmware.com/message/1401294</guid>
      <dc:date>2009-10-28T12:12:12Z</dc:date>
      <clearspace:dateToText>3 weeks, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Monitoring Memory Usage</title>
      <link>http://communities.vmware.com/message/1400035</link>
      <description>You run P2V for Windows? Did you clean already unpresent devices after P2V? VMTools installed? Also look at this &lt;a class="jive-link-external" href="http://communities.vmware.com/docs/DOC-5430"&gt;http://communities.vmware.com/docs/DOC-5430&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
StarWind Software R&amp;#38;D&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.starwindsoftware.com/"&gt;http://www.starwindsoftware.com&lt;/a&gt;</description>
      <pubDate>Tue, 27 Oct 2009 14:49:47 GMT</pubDate>
      <author>TobiasKracht</author>
      <guid>http://communities.vmware.com/message/1400035</guid>
      <dc:date>2009-10-27T14:49:47Z</dc:date>
      <clearspace:dateToText>3 weeks, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>opinions on the 10gb network cards</title>
      <link>http://communities.vmware.com/message/1399102</link>
      <description>Would like to know people's opinions on the 10gb network cards. In particular the "Intel 10 Gigabit AF DA Dual Port Server Adapter" and the "Chelsio Communications S320E: 10 Gbe Nework Adapter".&lt;br /&gt;
Just looking for horror stories.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">hardware</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">network</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">10gb</category>
      <pubDate>Mon, 26 Oct 2009 19:19:49 GMT</pubDate>
      <author>cxo</author>
      <guid>http://communities.vmware.com/message/1399102</guid>
      <dc:date>2009-10-26T19:19:49Z</dc:date>
      <clearspace:dateToText>3 weeks, 6 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>San Sizing documentation request...</title>
      <link>http://communities.vmware.com/message/1398471</link>
      <description>That's the trick with disk sizing - there's no such thing as a boilerplate recommendation.  &lt;br /&gt;
&lt;br /&gt;
Your LUN sizing will most often be dependent on the I/O characteristics you need for the device - IOps, disk throughput, etc.  The number of VMs you can reasonably place on a VM will also be limited by those numbers.  What I try to do when sizing my environments is figure out a baseline of peak (think worst-case application scenario here - what if all of the VMs' apps will be going nuts on the disk at the exact same time) IOps (that's usually the biggest disk bottleneck - physics are a pain here, as the head on a spindle can only be in one place at a time), figure out how many spindles I need to meet that.  Once I know the number of spindles my LUN has to be spread across, I can look at the overall size of the datastore that I'll need.  Keep in mind not only disk sizing here, but also whether or not VM snapshots will be put to use and for how long, and also keep in mind the memory being allocated to each of the VMs to plan for .vswp file sizing.  Once I have sizing information, I can look at the device split size on my storage array, figure out how many splits I need to meet both the I/O and size requirements for the data store, and then create the LUN keeping in mind RAID overhead.  A rule of thumb I still use is 1 physical spindle provides me with ~150 IOps to work with.  That number is very conservative (and frankly a bit old, but I haven't looked at disk in too much depth in the past 3 years).  Also keep in mind that your LUNs will be sharing spindles (and therefore, sharing IOps) with other LUNs, so other activity on the storage array needs to be taken into account during the design process as well.&lt;br /&gt;
&lt;br /&gt;
For example, If I have an environment with 10 applications, each with a peak IOps of 500, I would ultimately want a LUN that would support 5000 IOps.  Working with my 150 IOps rule of thumb, I would be looking at a LUN spanning 34 spindles.  If each of the VMs was provisioned with 50GB virtual disks and 4GB of RAM each, and I knew the VMs would not have any point that the snapshots would grow beyond 10% of the original virtual disk size, I would plan for 550GB for virtual disk/snapshot space, 40GB for .vswp files, and some overhead for VMFS metadata, config and log files, etc.  So I'd be looking at, say, a 600GB LUN.  At this point, can my storage array support a 600GB LUN spanning 34 spindles?  That's a 17.6GB split size.  Some compromise may need to be made depending on what you know of your application performance (is peak load going to happen all at once, or is the worst aggregate peak load lower?  that could lead to a larger split size and fewer spindles) or what you know of your storage array (split sizes are available larger and smaller than what the calculations show - do you go with a smaller split and more spindles, wasting available IO, or do you take the larger split size with fewer spindles, with the possibility of either starving yourself of IOps or wasting precious disk space).&lt;br /&gt;
&lt;br /&gt;
As for maximum numbers of VMs placed on a given data store, you wouldn't want many more than 32 VMs on each, largely due to the way VMFS file locking is maintained.  Each host will lock files in the metadata space for the VMFS datastore.  The locks are updated periodically.  Those updates, and any other metadata update activities, cause an entire SCSI device lock to be maintained on the disk device.  Above 32 heavily used VMs, metadata updates can easily keep the LUN in a locked state, preventing VM disk I/O from occurring.&lt;br /&gt;
&lt;br /&gt;
It's nearly impossible to put together a sweeping document because recommendations made for your environment are specific to your environment.  Sure, workloads between dissimilar shops are similar, but the subtleties of each shop means that any generalized recommendation like "build 500GB LUNs across 10 spindles and put 15 VMs on them" would be overkill for 45% of the shops looking, and would be a performance disaster for 45%, leaving a smallish 10% of environments happy and in a good comfort zone.&lt;br /&gt;
&lt;br /&gt;
Hope that makes some sense, and helps.&lt;br /&gt;
-jk</description>
      <pubDate>Mon, 26 Oct 2009 12:34:16 GMT</pubDate>
      <author>jjkrueger</author>
      <guid>http://communities.vmware.com/message/1398471</guid>
      <dc:date>2009-10-26T12:34:16Z</dc:date>
      <clearspace:dateToText>4 weeks, 4 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>vmware server performance benchmarks...</title>
      <link>http://communities.vmware.com/message/1398152</link>
      <description>&lt;br /&gt;
Thanks for the response. Are there any other metrics to follow other than vmmark scores?&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Mon, 26 Oct 2009 02:41:11 GMT</pubDate>
      <author>eggie</author>
      <guid>http://communities.vmware.com/message/1398152</guid>
      <dc:date>2009-10-26T02:41:11Z</dc:date>
      <clearspace:dateToText>4 weeks, 14 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Resource Pools</title>
      <link>http://communities.vmware.com/message/1396823</link>
      <description>They each have 64GB. &lt;br /&gt;
&lt;br /&gt;
The average is about 1.5 GB per VM. Some machines have as much as 8GB and i'm sure this has been over provisioned. &lt;br /&gt;
&lt;p /&gt;
Does anybody have a good working practice of how to monitor over provisioned virtual machines? I would love to be able to claim some memory back.</description>
      <pubDate>Fri, 23 Oct 2009 11:24:43 GMT</pubDate>
      <author>Mr G Grant</author>
      <guid>http://communities.vmware.com/message/1396823</guid>
      <dc:date>2009-10-23T11:24:43Z</dc:date>
      <clearspace:dateToText>1 month, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>A Newbie needs help in a big way....HELP!!!</title>
      <link>http://communities.vmware.com/message/1396407</link>
      <description>Aloha:&lt;br /&gt;
&lt;br /&gt;
I just installed VMware-Fusion-2.0.6-196839.dmg on My MacBook Pro running OS 10.5.8.  It seems to work well.&lt;br /&gt;
&lt;br /&gt;
However I am having problems installing a Hanger 9 simulator.  It's on 4 separate disks.   The first disk goes on ok asked for disk 2, but does not eject disk one.&lt;br /&gt;
&lt;br /&gt;
I get an error panel which is attached.&lt;br /&gt;
&lt;br /&gt;
Any ideas??&lt;br /&gt;
&lt;br /&gt;
Thanks &lt;br /&gt;
Dan Page</description>
      <pubDate>Thu, 22 Oct 2009 21:19:50 GMT</pubDate>
      <author>Dinube</author>
      <guid>http://communities.vmware.com/message/1396407</guid>
      <dc:date>2009-10-22T21:19:50Z</dc:date>
      <clearspace:dateToText>1 month, 1 day ago</clearspace:dateToText>
    </item>
    <item>
      <title>VA deployment degradation on vSphere4</title>
      <link>http://communities.vmware.com/message/1395763</link>
      <description>&lt;br /&gt;
Hello,&lt;br /&gt;
&lt;p /&gt;
We have high performance degradation when our Appliance is deployed to ESX server via Virtual Center. When the appliance is deployed to ESX directly we don&amp;rsquo;t have such problem.&lt;br /&gt;
We are using the following script:&lt;br /&gt;
&lt;p /&gt;
&lt;i&gt;curl -u username:NfelMC2Ub -k -T upload &lt;a class="jive-link-external" href="https://10.250.148.27/folder/LR1_11133_ESXAppliance/upload.dat?dcPath=Center&amp;#38;dsName=Storage1"&gt;https://10.250.148.27/folder/LR1_11133_ESXAppliance/upload.dat?dcPath=Center&amp;#38;dsName=Storage1&lt;/a&gt;&lt;/i&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
where 10.250.148.27 is the address of Virtual Center. If we specify the address of ESX instead of Virtual Center, everything works fast. &lt;br /&gt;
BTW such problem appeared on vSphere 4, on previous versions everything was fine.&lt;br /&gt;
Could you please answer:&lt;br /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;What could be the reason of this degradation? &lt;/li&gt;
&lt;li&gt;How can we tune up the speed of deployment via Virtual Center?&lt;/li&gt;
&lt;li&gt;If we have correct credentials on Virtual Center, is it possible to deploy directly to the ESX registered on it?&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
Thank you</description>
      <pubDate>Thu, 22 Oct 2009 11:08:21 GMT</pubDate>
      <author>Lexus16</author>
      <guid>http://communities.vmware.com/message/1395763</guid>
      <dc:date>2009-10-22T11:08:21Z</dc:date>
      <clearspace:dateToText>1 month, 2 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>IRQ interrrupts</title>
      <link>http://communities.vmware.com/message/1395680</link>
      <description>Yep, the IRQ is the number in the first column, so your host usb controller(s) are using IRQ 20 and 21 which isn't showing as sharing as per your first screenshot.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks,&lt;br /&gt;
Neil</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">irq</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">interrrupts</category>
      <pubDate>Thu, 22 Oct 2009 09:34:15 GMT</pubDate>
      <author>NTurnbull</author>
      <guid>http://communities.vmware.com/message/1395680</guid>
      <dc:date>2009-10-22T09:34:15Z</dc:date>
      <clearspace:dateToText>1 month, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Recommanded VM instances in 1 esx host 3.0 and 3.5</title>
      <link>http://communities.vmware.com/message/1395503</link>
      <description>&lt;br /&gt;
 I feel for quality performance...max 20 vm instances per esx host..of course its also depends on how powerful the esx host..&lt;br /&gt;
&lt;p /&gt;
I wonder if there are any calulation for  these ratio btw esx host and VM instances.</description>
      <pubDate>Thu, 22 Oct 2009 03:13:17 GMT</pubDate>
      <author>sean051</author>
      <guid>http://communities.vmware.com/message/1395503</guid>
      <dc:date>2009-10-22T03:13:17Z</dc:date>
      <clearspace:dateToText>1 month, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>Using vscsiStats for Storage Performance Analysis</title>
      <link>http://communities.vmware.com/docs/DOC-10095</link>
      <description>&lt;h1&gt;Introduction &lt;/h1&gt;
esxtop is a great tool for performance analysis of all types.  However, with only latency and throughput statistics, esxtop will not provide the full picture of the storage profile.  Furthermore, esxtop only provides latency numbers for Fibre Channel and iSCSI storage.  Latency analysis of NFS traffic is not possible with esxtop.&lt;br /&gt;
&lt;br /&gt;
Since ESX 3.5, VMware has provided a tool specifically for profiling storage: vscsiStats.  vscsiStats collects and reports counters on storage activity.  Its data is collected at the virtual SCSI device level in the kernel.  This means that results are reported per VMDK (or RDM) irrespective of the underlying storage protocol.  The following data are reported in histogram form:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;IO size&lt;/li&gt;
&lt;li&gt;Seek distance&lt;/li&gt;
&lt;li&gt;Outstanding IOs&lt;/li&gt;
&lt;li&gt;Latency (in microseconds)&lt;/li&gt;
&lt;li&gt;More!&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
&lt;h1&gt;Running vscsiStats&lt;/h1&gt;
vscsiStats collection and analysis requires two steps:&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;Start statistics collection.&lt;/li&gt;
&lt;li&gt;View accrued statistics.&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
Documentation on command-line parameters are available when running '/usr/lib/vmware/bin/vscsiStats -h'.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;Starting and Stopping vscsiStats Collection&lt;/h2&gt;
The tool is started with the following command:&lt;br /&gt;
&lt;pre class="jive-pre"&gt;&lt;code class="jive-code jive-plain"&gt;/usr/lib/vmware/bin/vscsiStats -s -w &amp;lt;world_group_id&amp;gt;
&lt;/code&gt;&lt;/pre&gt;&lt;br /&gt;
&lt;br /&gt;
This command starts the process that will accrue statistics.  The world group ID must be set to a running virtual machine.  The running VMs' IDs can be obtained by running '/usr/lib/vmware/bin/vscsiStats -l'.&lt;br /&gt;
&lt;br /&gt;
After about 30 minutes vscsiStats will stop running.  If the analysis is needed for a longer period, the start command should be repeated above in this window.  That will defer the timeout and termination by another 30 minutes.&lt;br /&gt;
&lt;br /&gt;
Since results are accrued and reported out in summary, the histograms will include data since collection was started.  To reset all counters to zero, run '/usr/lib/vmware/bin/vscsiStats -r'.&lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;Viewing Statistics&lt;/h2&gt;
Counters are displayed by using the following command:&lt;br /&gt;
&lt;pre class="jive-pre"&gt;&lt;code class="jive-code jive-plain"&gt;/usr/lib/vmware/bin/vscsiStats -p &amp;lt;histo_type&amp;gt; [-c]
&lt;/code&gt;&lt;/pre&gt;&lt;br /&gt;
&lt;br /&gt;
The histogram type is used to specify either all of the statistics or one group of them.  Options include all, ioLength, seekDistance, outstandingIOs, latency, interarrival.&lt;br /&gt;
&lt;br /&gt;
Results can be produced in a more compact comma-delimited list by adding the optional "-c" above.&lt;br /&gt;
&lt;br /&gt;
&lt;h1&gt;Using vscsiStats Results&lt;/h1&gt;
&lt;h2&gt;Use Case 1: Identifying Sequential IO&lt;/h2&gt;
Storage arrays can process sequential IO much faster than random IO.  You can therefore improve the performance of a sequential workload by placing it on a dedicated LUN to allow the array to optimize access.  vscsiStats can help you identify your sequential workloads even if you don't understand anything about the application in the VM.&lt;br /&gt;
&lt;br /&gt;
Take the following graph as example, which I generated by running '/usr/lib/vmware/bin/vscsiStats -p seekDistance':&lt;br /&gt;
&lt;br /&gt;
&lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/102-10095-6-5910/random_write_histo.png" alt="random_write_histo.png" width="620" class="jive-image-thumbnail jive-image" onclick="myJiveImage.start(this, 'http://communities.vmware.com/servlet/JiveServlet/downloadImage/102-10095-6-5910/random_write_histo.png');return false;"/&gt;  &lt;br /&gt;
&lt;br /&gt;
This graph shows that most of the commands are being issued a great distance from the previous command.  It looks like all of the commands were 50,000 or more logical blocks away from the previous command.  When I looked at the raw data, I saw that over 99% of the commands were more than 128 blocks away from the previous command.  That's random access if I've ever seen it.  Here's the opposite example:&lt;br /&gt;
&lt;br /&gt;
&lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/102-10095-6-5908/sequential_write_histo.png" alt="sequential_write_histo.png" width="620" class="jive-image-thumbnail jive-image" onclick="myJiveImage.start(this, 'http://communities.vmware.com/servlet/JiveServlet/downloadImage/102-10095-6-5908/sequential_write_histo.png');return false;"/&gt;&lt;br /&gt;
&lt;br /&gt;
In this case the logical block number (LBN) of each command is most frequently exactly one larger than the previous command.  That's the signature of a heavily sequential workload.  It shouldn't surprise you to learn that both of these profiles were generated by Iometer using random and sequential writes, respectively. &lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;Use Case 2: Optimizing for IO Sizes&lt;/h2&gt;
The IO size is an important characteristic of storage profiles.  A variety of best practices have been provided by storage vendors to enable customers to tune their storage to a particular IO size.  As an example, it may make sense to optimize an array's stripe size to its average IO size.  vscsiStats can provide a histogram of IO sizes to help this process.  The following graph was generated by '/usr/lib/vmware/bin/vscsiStats -p ioLength':&lt;br /&gt;
&lt;br /&gt;
&lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/102-10095-6-5911/io_size_4k.png" alt="io_size_4k.png" width="620" class="jive-image-thumbnail jive-image" onclick="myJiveImage.start(this, 'http://communities.vmware.com/servlet/JiveServlet/downloadImage/102-10095-6-5911/io_size_4k.png');return false;"/&gt; &lt;br /&gt;
&lt;br /&gt;
From these results I can see that about a quarter of the commands came in IOs smaller than 4k.  About half of the commands were sized to 4k commands.  The minute number of remaining IOs were larger than 4k.  This signature is common of a VMDK formatted to 4k blocks and supporting OS and application execution.  The storage array should be optimized for 4k blocks if this disk's performance is a priority. &lt;br /&gt;
&lt;br /&gt;
&lt;h2&gt;Use Case 3: Storage Latency Analysis (Including NFS!)&lt;/h2&gt;
esxtop is a terrific tool for latency-based storage analysis.  Fibre Channel and iSCSI HBAs have device and kernel latencies in esxtop's storage panel.  Software iSCSI initiators will show up as vmhba32 (ESX 3.5 and earlier) and vmhba33 (ESX 4.0 and later.)  But esxtop does not provide latency statistics for NFS stores.&lt;br /&gt;
&lt;br /&gt;
Because vscsiStats collects its results where the guest interacts with the hypervisor, it is unaware of the storage implementation.  Latency statistics can be collected for all storage configurations with this tool.&lt;br /&gt;
&lt;br /&gt;
&lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/102-10095-6-5917/latency.png" alt="latency.png" width="620" class="jive-image-thumbnail jive-image" onclick="myJiveImage.start(this, 'http://communities.vmware.com/servlet/JiveServlet/downloadImage/102-10095-6-5917/latency.png');return false;"/&gt;&lt;br /&gt;
&lt;br /&gt;
The above graph shows that the server in my office with a single direct-attached SCSI disk is performing as I would expect.  About half of all the operations are completing in under 5 ms.  The other half take 5-15 ms to complete.  A few commands took longer than 15 ms, but the number is so small that it doesn't concern me.  Similar results can be seen with NFS arrays.&lt;br /&gt;
&lt;br /&gt;
&lt;h1&gt;vscsiStats on ESXi&lt;/h1&gt;
vscsiStats can be installed on ESXi hosts after putting the host into tech support mode.  More information on this process is availalble on &lt;a class="jive-link-external" href="http://vpivot.com/2009/10/21/vscsistats-for-esxi/"&gt;Scott's blog on the subject on vPivot&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;h1&gt;Additional Resources&lt;/h1&gt;
My colleagues Ajay Gulati, Chethan Kumar, and Irfan Ahmad presented at VPACT 09 &lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-10104" title="This paper presents workload characterization study of three top-tier enterprise applications using VMware ESX server hypervisor. We further separate out different components (for example data, index and redo log in a database) of these workloads to understand their behavior in isolation.  We find that most workloads show highly random access patterns. Next, we study the impact of storage consolidation on workloads (both random and sequential) and their burstiness."&gt;Storage Workload Characterization and Consolidation in Virtualized Enviornments&lt;/a&gt;.  This paper serves as an excellent example of vscsiStats in action.&lt;br /&gt;
&lt;br /&gt;
I learned vscsiStats by reviewing Irfan's VMworld 2007 presentation (&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-10084" title="The presentation deck delivered by Irfan Ahman at VMworld 2007.  This details a powerful storage analysis tool that has been packaged since ESX 3.5."&gt;vscsiStats: Fast and Easy Disk Workload Characterization on VMware ESX Server&lt;/a&gt;) and playing with the tool.  Check out his presentation if you'd like more detail.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vscsistats</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">analysis</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">iscsi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">nfs</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">storage</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">san</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">nas</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">disk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vmfs</category>
      <pubDate>Fri, 29 May 2009 22:28:27 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/docs/DOC-10095</guid>
      <dc:date>2009-05-29T22:28:27Z</dc:date>
      <clearspace:dateToText>1 month, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>Listing hosts from a failed VM ESX 3.5 server crash</title>
      <link>http://communities.vmware.com/message/1394179</link>
      <description>In our instance, all of the servers were migrated to other ESX servers and the one that crashed was put in maintenance mode for diagnosis.  We have about 15 ESX servers with about 200 hosts.  We need to know what servers were on the ESX at a point in time.</description>
      <pubDate>Tue, 20 Oct 2009 21:41:20 GMT</pubDate>
      <author>Just_Bob</author>
      <guid>http://communities.vmware.com/message/1394179</guid>
      <dc:date>2009-10-20T21:41:20Z</dc:date>
      <clearspace:dateToText>1 month, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Slow Network for 1000/Full Host, Fast Network for Guests?</title>
      <link>http://communities.vmware.com/message/1394066</link>
      <description>&lt;br /&gt;
I know this is an old thread, but the descriptions here are indicating that it might be a shared IRQ issue that is affecting the throughput on the service console nic.&lt;br /&gt;
&lt;p /&gt;
 KB1003710 has all the info.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx3.5</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">network</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">networking</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vlan</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vswitch</category>
      <pubDate>Tue, 20 Oct 2009 19:42:48 GMT</pubDate>
      <author>Jamie Rix</author>
      <guid>http://communities.vmware.com/message/1394066</guid>
      <dc:date>2009-10-20T19:42:48Z</dc:date>
      <clearspace:dateToText>1 month, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>17</clearspace:replyCount>
    </item>
    <item>
      <title>Degradation when snapshots are deleted?</title>
      <link>http://communities.vmware.com/message/1394022</link>
      <description>No problem, snapshots are often misunderstood, especially by those new to VMware. Once you start playing around with them and getting to know more about them it becomes easier to understand how they work and the impacts of using them.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Eric Siebert&lt;br /&gt;
VMware Communities User Moderator&lt;br /&gt;
-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-&lt;br /&gt;
Author of the upcoming book "VMware VI3 Implementation and Administration" now available on &lt;a class="jive-link-external" href="http://my.safaribooksonline.com/9780137008612"&gt;Rough Cuts&lt;/a&gt;&lt;br /&gt;
Check out my website: &lt;a class="jive-link-external" href="http://vmware-land.com"&gt;VMware-land&lt;/a&gt;&lt;br /&gt;
Read my virtualization blog: &lt;a class="jive-link-external" href="http://servervirtualization.blogs.techtarget.com/category/eric-siebert/"&gt;SSV Blog&lt;/a&gt;&lt;br /&gt;
-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-</description>
      <pubDate>Tue, 20 Oct 2009 18:23:08 GMT</pubDate>
      <author>esiebert7625</author>
      <guid>http://communities.vmware.com/message/1394022</guid>
      <dc:date>2009-10-20T18:23:08Z</dc:date>
      <clearspace:dateToText>1 month, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Performance issue when deleting snapshot</title>
      <link>http://communities.vmware.com/message/1393744</link>
      <description>Thanks, i have already this configuration.</description>
      <pubDate>Tue, 20 Oct 2009 14:51:24 GMT</pubDate>
      <author>chrisAMS</author>
      <guid>http://communities.vmware.com/message/1393744</guid>
      <dc:date>2009-10-20T14:51:24Z</dc:date>
      <clearspace:dateToText>1 month, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>ESX 3.5 VM Perfomance Charting</title>
      <link>http://communities.vmware.com/message/1392806</link>
      <description>&lt;br /&gt;
ESX 3.5 (build 163429) Virtual Center 2.5 (build 147633)&lt;br /&gt;
&lt;p /&gt;
In our environment, we have a predominance of WIndows servers. When asked for VM performance data, we typically recommend the client perfom OS level performance monitoring for detailed information. There are an increasing amount of requests where Virtual Center metrics and performance charts suffice and I see us getting more requests to provide this level of perfomance data and charting.&lt;br /&gt;
&lt;p /&gt;
When charting in Virtual Center, I notice that realtime data has more metric options than day, week, month, year and custom. Particularly in disk, outside of real-time, I only have  a disk usage metric.&lt;br /&gt;
&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;First, is what I descrie what I should expect to see?&lt;/li&gt;
&lt;li&gt;Is there a configuration option (or detail option) I can set to allow those metrics to be chartable in the other time frames?&lt;/li&gt;
&lt;li&gt;If there is, is it wise to make that change (will it have potential negative effects)?&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
Any information about performance charting for VMs withing Virtual Center would be helpful.</description>
      <pubDate>Mon, 19 Oct 2009 16:53:45 GMT</pubDate>
      <author>vmproteau</author>
      <guid>http://communities.vmware.com/message/1392806</guid>
      <dc:date>2009-10-19T16:53:45Z</dc:date>
      <clearspace:dateToText>1 month, 4 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Microsoft Dynamics NAV/Windows Server 2008 performance problems</title>
      <link>http://communities.vmware.com/message/1392483</link>
      <description>&lt;br /&gt;
Except setting JumboFrame to 9k you also have to change following registry parametrs in HKLM\System\CurrentControlSet\Services\Tcpip\Parametres:&lt;br /&gt;
&lt;p /&gt;
GlobalMaxTcpWinowSize=0x01400000&lt;br /&gt;
TcpWindowSize=0x01400000&lt;br /&gt;
Tcp1323Opts=3&lt;br /&gt;
SackOpts=1.&lt;br /&gt;
&lt;p /&gt;
All paramets are DWORD type, and after applying you have to reboot server. &lt;br /&gt;
&lt;p /&gt;
StarWind Software R&amp;#38;D</description>
      <pubDate>Mon, 19 Oct 2009 11:38:40 GMT</pubDate>
      <author>TobiasKracht</author>
      <guid>http://communities.vmware.com/message/1392483</guid>
      <dc:date>2009-10-19T11:38:40Z</dc:date>
      <clearspace:dateToText>1 month, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>ESX SAN Sizing (HA, VMotion)</title>
      <link>http://communities.vmware.com/message/1392286</link>
      <description>The C:/D: thery could be used but not necessary will improve your I/O speed.&lt;br /&gt;
You must check on your storage documentation if there are some best practices for RAID, LUN, multipath and so on...&lt;br /&gt;
You can split OS / Data disk only for guest that really need this.&lt;br /&gt;
&lt;br /&gt;
Andre</description>
      <pubDate>Mon, 19 Oct 2009 05:03:03 GMT</pubDate>
      <author>AndreTheGiant</author>
      <guid>http://communities.vmware.com/message/1392286</guid>
      <dc:date>2009-10-19T05:03:03Z</dc:date>
      <clearspace:dateToText>1 month, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Centos 5 VM 100% CPU usage</title>
      <link>http://communities.vmware.com/message/1392265</link>
      <description>&lt;br /&gt;
Hi, sorry for the late reply, been busy preparing for my wedding.&lt;br /&gt;
&lt;p /&gt;
I did what you asked...installed vmware tools and messed with the time settings so now I'm in a wait and see mode &lt;br /&gt;
&lt;p /&gt;
By mid  week I should know if the changes made any difference. The server sofware is Cumis, its a database for Credit Unions&lt;br /&gt;
&lt;p /&gt;
from a Trinidadian company named MSD, Micro Software Design.&lt;br /&gt;
&lt;p /&gt;
Thanks much for your help...I'm trying to get a hold on the features of ESXi, seems a very useful tool.</description>
      <pubDate>Mon, 19 Oct 2009 05:02:08 GMT</pubDate>
      <author>godpickny</author>
      <guid>http://communities.vmware.com/message/1392265</guid>
      <dc:date>2009-10-19T05:02:08Z</dc:date>
      <clearspace:dateToText>1 month, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>reinstalling after time machine back up</title>
      <link>http://communities.vmware.com/message/1391816</link>
      <description>Hi there,&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
I'm about to replace the hard drive in my mac book, I plan to reinstall everything&lt;br /&gt;
from time machine.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Has anybody done this? are there any special issues with VMware or XP, will all my XP&lt;br /&gt;
data be OK or should I reinstall it separately?&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
Thanks in advance. &lt;br /&gt;
&lt;p /&gt;
PS I&amp;rsquo;m running Mac 10.5.8  VM ware&lt;br /&gt;
2.00 Windows XP.</description>
      <pubDate>Sat, 17 Oct 2009 10:16:56 GMT</pubDate>
      <author>phydaux</author>
      <guid>http://communities.vmware.com/message/1391816</guid>
      <dc:date>2009-10-17T10:16:56Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>Is ESX a lot better than vmware server in performance??</title>
      <link>http://communities.vmware.com/message/1391614</link>
      <description>&lt;br /&gt;
Yes.  ESX (as well as ESXi) is much better than VMware Server.  Check out this graph from some old data the perf team generated for VMworld a couple of years ago:&lt;br /&gt;
&lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/2-1391614-7329/Picture+1.png" alt="Picture 1.png" width="450" class="jive-image-thumbnail jive-image" onclick="myJiveImage.start(this, 'http://communities.vmware.com/servlet/JiveServlet/downloadImage/2-1391614-7329/Picture+1.png');return false;"/&gt; &lt;br /&gt;
&lt;p /&gt;
This is basically equivalent systems running VMmark with either ESX or Server.  I believe these results were done on ESX 3.0.1.  ESX performance has improved much more than Server in the past two years, too. &lt;br /&gt;
&lt;p /&gt;
Scott&lt;br /&gt;
&lt;p /&gt;
More information on my blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://vpivot.com"&gt;http://vpivot.com&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds"&gt;http://twitter.com/drummonds&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vmware</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">server</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <pubDate>Fri, 16 Oct 2009 20:54:15 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/message/1391614</guid>
      <dc:date>2009-10-16T20:54:15Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>IBM LS22 server and Windows 2008 Terminal Server CPU Maxing Issue</title>
      <link>http://communities.vmware.com/message/1391400</link>
      <description>&lt;br /&gt;
I am running VM4 Sphere with a guest OS of Windows 2008 Terminal server on an IBM LS22 with 16 gigs of ram and 2 cpu's after the fith person logs in to the Win 2008  Terminal Server the cpu hits 100% on the virtual machine. &lt;br /&gt;
&lt;p /&gt;
My assuption is that its an issue with Windows 2008 TS ,but thought I would do a post here to see if anyone could shed some light on the issue. &lt;br /&gt;
&lt;p /&gt;
The system runs to a crawl after this happens and I haven't been able to run any other virutal machines. &lt;br /&gt;
&lt;p /&gt;
This server is Runing VM V4 sphere  &lt;br /&gt;
&lt;p /&gt;
I've been runing V 3 with out an issue, but  the new Sphere V4 seems to be buggy. &lt;br /&gt;
&lt;p /&gt;
Any suggestions about what could be causing this issue would be helpful.&lt;br /&gt;
&lt;p /&gt;
So to recap my questions are: &lt;br /&gt;
&lt;p /&gt;
Is this a vmware issue or just an Guest OS issue?&lt;br /&gt;
&lt;p /&gt;
If it is a vmware issue what could be causing the guest OS to spike to 100% on both cpus?&lt;br /&gt;
&lt;p /&gt;
Thank You &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Fri, 16 Oct 2009 16:31:33 GMT</pubDate>
      <author>Nemus</author>
      <guid>http://communities.vmware.com/message/1391400</guid>
      <dc:date>2009-10-16T16:31:33Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>Memory balooning &amp;#38; performance</title>
      <link>http://communities.vmware.com/message/1390828</link>
      <description>&lt;br /&gt;
We recently released a paper on ESX memory management, which included balloon and swap performance.  See &lt;a class="jive-link-external" href="http://vpivot.com/2009/09/25/esx-memory-management-ballooning-rules/"&gt;my blog on the subject&lt;/a&gt;.&lt;br /&gt;
&lt;p /&gt;
Scott&lt;br /&gt;
&lt;br /&gt;
More information on my blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://vpivot.com"&gt;http://vpivot.com&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds"&gt;http://twitter.com/drummonds&lt;/a&gt;</description>
      <pubDate>Thu, 15 Oct 2009 22:45:31 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/message/1390828</guid>
      <dc:date>2009-10-15T22:45:31Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>IOmega ix4-200d IOmeter results (100MB/Full Network)</title>
      <link>http://communities.vmware.com/docs/DOC-10925</link>
      <description />
      <pubDate>Thu, 15 Oct 2009 21:07:59 GMT</pubDate>
      <author>khughes</author>
      <guid>http://communities.vmware.com/docs/DOC-10925</guid>
      <dc:date>2009-10-15T21:07:59Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>10G Network Performance - max 1.6Gb/s</title>
      <link>http://communities.vmware.com/message/1390409</link>
      <description>&lt;br /&gt;
Have you checked your server to verify that it can handle this load?  Is the PCI slot PCIe 2?&lt;br /&gt;
&lt;p /&gt;
 JP</description>
      <pubDate>Thu, 15 Oct 2009 15:11:35 GMT</pubDate>
      <author>jpdicicco</author>
      <guid>http://communities.vmware.com/message/1390409</guid>
      <dc:date>2009-10-15T15:11:35Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Giving CPU Reservation to VM DRASTICALLY Improves Performance</title>
      <link>http://communities.vmware.com/message/1390104</link>
      <description>&lt;br /&gt;
I see a similar issue regularly on several Redhat 5.2 VM guests in all our ESX clusters.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Symptoms:&lt;br /&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;Very bad performance&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;High CPU load in performance view in VC&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;Processes (such as top) running in the VM guest take up much more CPU than normal&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;Ping localhost gives averages of about 0.4ms (which should be around 0.04)&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Fix:&lt;br /&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;Setting a small reservation (100Mhz) until ping time is normal (~0.04) again (takes up to 2 minutes)  &lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;Remove reservation&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;Repeat when issue happens again &lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
I have only seen this with 2 vCPU VM's. We run patch level 123630.</description>
      <pubDate>Thu, 15 Oct 2009 09:17:40 GMT</pubDate>
      <author>geertayan</author>
      <guid>http://communities.vmware.com/message/1390104</guid>
      <dc:date>2009-10-15T09:17:40Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>Understanding Performance</title>
      <link>http://communities.vmware.com/docs/DOC-5250</link>
      <description>&lt;br /&gt;
The following documents will explain some of the principles for virtual system performance. Please check back as we grow the number of articles here with time.&lt;br /&gt;
&lt;br /&gt;
ESX and Guest Operating Systems &lt;br /&gt;
&lt;p /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-9882"&gt;ESX Monitor Modes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-3580"&gt;Linux Timer Rate&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
CPU and Scheduling&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-5101"&gt;Hyper-Threading on ESX Server&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-7390"&gt;Ready Time&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-5501"&gt;VMkernel Scheduler&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-4960"&gt;Co-scheduling SMP VMs in VMware ESX Server&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Memory&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-6912"&gt;Large Memory Pages&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Network&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-10892"&gt;Advanced Networking Performance Options&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Storage &lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-9696"&gt;Storage Performance: VMFS and Protocols&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-6490"&gt;Storage Queues and Performance&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vmfs</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">storage</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">cpu</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">kernel</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">scheduling</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">smp</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">monitor</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">network</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">memory</category>
      <pubDate>Fri, 16 May 2008 21:30:03 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/docs/DOC-5250</guid>
      <dc:date>2008-05-16T21:30:03Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>ESX Network configuration samples</title>
      <link>http://communities.vmware.com/message/1388858</link>
      <description>Flyinverted,&lt;br /&gt;
  I like your config except for one thing: you are using both onboard ports on 1 vswitch.  You should use 1 onboard and 1 PCI vmnic on the same switch for redundancy across controllers as well.  It seems like a small issue until you lose both onboard ports...&lt;br /&gt;
&lt;br /&gt;
JP</description>
      <pubDate>Tue, 13 Oct 2009 21:58:33 GMT</pubDate>
      <author>jpdicicco</author>
      <guid>http://communities.vmware.com/message/1388858</guid>
      <dc:date>2009-10-13T21:58:33Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>How to check total Ram in the ESX host</title>
      <link>http://communities.vmware.com/message/1387500</link>
      <description>I had a similar requirement a while back to find out what the configuration of the RAM and total amounts were. The following worked quite well for me:&lt;br /&gt;
&lt;br /&gt;
dmidecode | grep "Size"&lt;br /&gt;
&lt;p /&gt;
You'll get something like this:&lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;Size: 4096 MB&lt;/b&gt;&lt;br /&gt;
&lt;b&gt;Size: 4096 MB&lt;/b&gt;&lt;br /&gt;
&lt;b&gt;Size: 4096 MB&lt;/b&gt;&lt;br /&gt;
&lt;b&gt;Size: 4096 MB&lt;/b&gt;&lt;br /&gt;
Size: No Module Installed&lt;br /&gt;
Size: No Module Installed&lt;br /&gt;
Size: No Module Installed&lt;br /&gt;
Size: No Module Installed&lt;br /&gt;
&lt;p /&gt;
Therefore 4 x 4096 = 16GB</description>
      <pubDate>Mon, 12 Oct 2009 16:01:30 GMT</pubDate>
      <author>a2alpha</author>
      <guid>http://communities.vmware.com/message/1387500</guid>
      <dc:date>2009-10-12T16:01:30Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Cas Latancy and Vmmware VMs</title>
      <link>http://communities.vmware.com/message/1387140</link>
      <description>If you are not perfomance geek, or not using high perfomance and hign availability database with with a lot of requests - it`s not.&lt;br /&gt;
&lt;br /&gt;
StarWind Software R&amp;#38;D</description>
      <pubDate>Mon, 12 Oct 2009 09:34:50 GMT</pubDate>
      <author>TobiasKracht</author>
      <guid>http://communities.vmware.com/message/1387140</guid>
      <dc:date>2009-10-12T09:34:50Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Horrible performance after long inactivity</title>
      <link>http://communities.vmware.com/message/1386591</link>
      <description>&lt;br /&gt;
I am running a Windows XP (32-bit) guest on an Ubuntu 9.04 (64-bit) host using VMPlayer 2.5.3. Performance was marginal until I set "sched.mem.pshare.enable" and "mainMem.useNamedFile" to FALSE. Now performance is very good with one major exception:&lt;br /&gt;
&lt;p /&gt;
 If I leave the guest  running overnight, when I start using it again n the morning, the performance is absolutely horrible until I reboot the guest. This morning, from clicking "Start" to clicking "Turn off this computer" was 45 sec. It took about 15 min to reboot the guest.&lt;br /&gt;
&lt;p /&gt;
Is there a memory leak in VMPlayer or some other issue that causes performance to degrade over time? Is there an issue with suspend on the guest that causes somethig similar (maybe WIndows XP Power Saving or Suspend features)? &lt;br /&gt;
&lt;p /&gt;
The host has 6GB of memory. I have 2GB allocated to the guest. The pertinetn information is below:&lt;br /&gt;
&lt;p /&gt;
        memsize = "2048"&lt;br /&gt;
        MemAllowAutoScaleDown = "FALSE"&lt;br /&gt;
        sched.mem.pshare.enable = "FALSE"&lt;br /&gt;
        mainMem.useNamedFile = "FALSE"&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vmplayer</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">ubuntu</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">jaunty</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">windows_xp</category>
      <pubDate>Sat, 10 Oct 2009 20:48:47 GMT</pubDate>
      <author>jkounis</author>
      <guid>http://communities.vmware.com/message/1386591</guid>
      <dc:date>2009-10-10T20:48:47Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>performance problems and vmi soon depricated?</title>
      <link>http://communities.vmware.com/message/1384888</link>
      <description>This may help: &lt;a class="jive-link-external" href="http://www.vmware.com/resources/techresources/10006"&gt;Performance Evaluation of Intel EPT Hardware Assist&lt;/a&gt;.</description>
      <pubDate>Thu, 08 Oct 2009 15:22:38 GMT</pubDate>
      <author>jmattson</author>
      <guid>http://communities.vmware.com/message/1384888</guid>
      <dc:date>2009-10-08T15:22:38Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>How to handle Vendor\Application requirements (physical) in VMWare</title>
      <link>http://communities.vmware.com/message/1383952</link>
      <description>thanks for the response but that's not what i'm after.  There has to be some guideline to translate physical server requirements to virtual requirements.  If not, then every vendor asking for 4 CPU and 8 GB RAM will be insisting on VMs built with those stats.  that can't possibly be VMWare's acceptale practice.</description>
      <pubDate>Wed, 07 Oct 2009 18:38:36 GMT</pubDate>
      <author>gbattiston</author>
      <guid>http://communities.vmware.com/message/1383952</guid>
      <dc:date>2009-10-07T18:38:36Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>ballooned performance counter</title>
      <link>http://communities.vmware.com/message/1383846</link>
      <description>The balloon driver is implemented as a device driver in the guest OS.  As it inflates it takes memory from the guest and pins that memory so the guest cannot reclaim or use it.  The memory is still visible to the guest, but unavailable.&lt;br /&gt;
&lt;br /&gt;
By setting a memory limit to the VM you have asked the kernel to reduce the VM's memory footprint through ballooning or swapping.  Because &lt;a class="jive-link-external" href="http://www.vmware.com/resources/techresources/10062"&gt;ballooning is so much more efficient that swapping&lt;/a&gt;, the balloon driver inflates first.&lt;br /&gt;
&lt;br /&gt;
To understand the fluctuations, you would need to check swap activity on the same VM and ballooning and swap activity on other VMs.  All of these activities are interrelated. &lt;br /&gt;
&lt;br /&gt;
Scott&lt;br /&gt;
&lt;br /&gt;
More information on my blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://vpivot.com"&gt;http://vpivot.com&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds"&gt;http://twitter.com/drummonds&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">balloon</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance_counters</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">memory</category>
      <pubDate>Wed, 07 Oct 2009 16:20:04 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/message/1383846</guid>
      <dc:date>2009-10-07T16:20:04Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>VMWare performance resources</title>
      <link>http://communities.vmware.com/message/1383755</link>
      <description>Oh and just saw the last bit of your post again, it's not just degredation, some apps/workload benifit from being virtualised. I'd be a bit more specific on apps as there are loads of people on the communities that would be able to lend a hand and some real world experience - not just cold hard lab tests&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks,&lt;br /&gt;
Neil</description>
      <pubDate>Wed, 07 Oct 2009 15:02:17 GMT</pubDate>
      <author>NTurnbull</author>
      <guid>http://communities.vmware.com/message/1383755</guid>
      <dc:date>2009-10-07T15:02:17Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Per-VM I/O Monitoring On NFS Datastores</title>
      <link>http://communities.vmware.com/message/1383490</link>
      <description>Thanks for the replies!&lt;br /&gt;
&lt;br /&gt;
Good to know that VMware is aware of the issue and seem to be working on a solution at least. Too bad that it seems so far away though.&lt;br /&gt;
&lt;br /&gt;
I've been able to trace the file handlers used in NFS Lookup request/replies to specific files/directories (and thus determine the VMs). I've managed to filter out packets matching these file handlers with tshark in a way that i can see (and measure) the specific traffic when a VM powers on/off. However, further operations to the "disk" in the OS of the VMs don't use these file handlers. I can't trace the actual I/O, because most of that traffic is NFS FILE_SYNC packages (which have no human readable payload displaying file or directory, like the lookup packages have) and they use different file handlers than the NFS lookup packages. Too bad. Maybe there are some NFS gurus around that can nudge me in the right direction? Or suggestions about other possible workarounds?</description>
      <pubDate>Wed, 07 Oct 2009 12:07:16 GMT</pubDate>
      <author>deltajoka</author>
      <guid>http://communities.vmware.com/message/1383490</guid>
      <dc:date>2009-10-07T12:07:16Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>.</title>
      <link>http://communities.vmware.com/message/1382170</link>
      <description>.</description>
      <pubDate>Tue, 06 Oct 2009 05:50:28 GMT</pubDate>
      <author>Scissor</author>
      <guid>http://communities.vmware.com/message/1382170</guid>
      <dc:date>2009-10-06T05:50:28Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Slow RAM performance- is this normal?</title>
      <link>http://communities.vmware.com/message/1382211</link>
      <description>&lt;br /&gt;
Hi..  &lt;br /&gt;
&lt;p /&gt;
As this is a NUMA system, I would verify that Node Interleaving is disabled in the BIOS... Just to make sure that there's no VMs being assigned memory on a different node than the CPU it's running on.. If this happens there might be performance degradition in the VM. Even though ESX is NUMA aware and will try to CPU and mem on the same node, you never know.&lt;br /&gt;
&lt;p /&gt;
The number of VMs dosn't indicate the actual number of physical CPUs in the system..  &lt;br /&gt;
Don't know what version you're running, but in vSphere4, as an example, you can have 20 vCPUs per physical core according to docs.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
/Rubeck</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">ram</category>
      <pubDate>Tue, 06 Oct 2009 07:12:47 GMT</pubDate>
      <author>Rubeck</author>
      <guid>http://communities.vmware.com/message/1382211</guid>
      <dc:date>2009-10-06T07:12:47Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>esxtop reports wrong zero values for CPU and Memory (Service Console)</title>
      <link>http://communities.vmware.com/message/1381725</link>
      <description>&lt;br /&gt;
Hi!&lt;br /&gt;
&lt;p /&gt;
 Yes i have already read the complete document and used it while the implementation. The interesting thing is&lt;br /&gt;
&lt;p /&gt;
CCPU Context Switches has correct values but&lt;br /&gt;
&lt;p /&gt;
CCPU Idle Time / Usertime / Systemtime and Waittime have zero values which seems to be wrong.The&lt;br /&gt;
&lt;p /&gt;
esxtop interactively shows us values for these parameters!  Next to this it is the Disk performance data&lt;br /&gt;
&lt;p /&gt;
(not memory ... memory values are ok! My mistake!). CMDs/a READS/s WRITE/s MBREAD/s and&lt;br /&gt;
&lt;p /&gt;
MBWRTN/s report zero values all the time?&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Any further idea ... ?&lt;br /&gt;
&lt;p /&gt;
 Kind regards ...&lt;br /&gt;
&lt;p /&gt;
 Timo &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Mon, 05 Oct 2009 17:29:52 GMT</pubDate>
      <author>Timo1970</author>
      <guid>http://communities.vmware.com/message/1381725</guid>
      <dc:date>2009-10-05T17:29:52Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Any Performance Advantages Using Multiple Virtual Hard Disks? (eg, SQL Server)</title>
      <link>http://communities.vmware.com/message/1381675</link>
      <description>&lt;br /&gt;
Thanks for the replies everyone. Almost there.... What about when you're VMDK's are on NFS shares (like ours!)?</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">sql</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">virtual</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">disks</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">multiple</category>
      <pubDate>Mon, 05 Oct 2009 16:57:02 GMT</pubDate>
      <author>DonJuanJovi</author>
      <guid>http://communities.vmware.com/message/1381675</guid>
      <dc:date>2009-10-05T16:57:02Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>CPU Utilization More</title>
      <link>http://communities.vmware.com/message/1379785</link>
      <description>&lt;br /&gt;
Can you give additional information:&lt;br /&gt;
&lt;p /&gt;
SAS controller&lt;br /&gt;
&lt;p /&gt;
number and types of HDD&lt;br /&gt;
&lt;p /&gt;
types of RAID areas&lt;br /&gt;
&lt;p /&gt;
logs from RAID controller (what process is going on?)&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!&lt;br /&gt;
&lt;p /&gt;
VSP4, VTSP4, VCP4&lt;br /&gt;
ITIL v.3 Foundation</description>
      <pubDate>Fri, 02 Oct 2009 10:41:31 GMT</pubDate>
      <author>nanev</author>
      <guid>http://communities.vmware.com/message/1379785</guid>
      <dc:date>2009-10-02T10:41:31Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Any known ways to increase Video Ram?</title>
      <link>http://communities.vmware.com/message/1379474</link>
      <description>I do not believe this is possible, but out of curiosity, why do you want/need to do this?</description>
      <pubDate>Thu, 01 Oct 2009 23:36:56 GMT</pubDate>
      <author>sflanders</author>
      <guid>http://communities.vmware.com/message/1379474</guid>
      <dc:date>2009-10-01T23:36:56Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Disk write speed is very slow with Dell SAS 6/iR controller</title>
      <link>http://communities.vmware.com/message/1379116</link>
      <description>&lt;br /&gt;
I have a 610 and by default it has a battery back cache.&lt;br /&gt;
&lt;p /&gt;
You have to specifically tell it to run with a writeback cache if you don't have a battry.&lt;br /&gt;
&lt;p /&gt;
See the dell documentation.&lt;br /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://www.dell.com/content/topics/topic.aspx/global/products/pvaul/topics/en/us/raid_controller?c=us&amp;#38;l=en&amp;#38;cs=555"&gt;http://www.dell.com/content/topics/topic.aspx/global/products/pvaul/topics/en/us/raid_controller?c=us&amp;#38;l=en&amp;#38;cs=555&lt;/a&gt;</description>
      <pubDate>Thu, 01 Oct 2009 16:28:26 GMT</pubDate>
      <author>LucasAlbers</author>
      <guid>http://communities.vmware.com/message/1379116</guid>
      <dc:date>2009-10-01T16:28:26Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Stress and Volume Testing</title>
      <link>http://communities.vmware.com/message/1378853</link>
      <description>Yes SVT could adversely affect the performance of other VMs depending on how your environment is designed - remember the VMs are sharing the resources with the VM/application being tested - so for example if you have a saturated a path storage the added load of the testing will affect the other VMs ability to access the storage - &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful</description>
      <pubDate>Thu, 01 Oct 2009 13:07:57 GMT</pubDate>
      <author>weinstein5</author>
      <guid>http://communities.vmware.com/message/1378853</guid>
      <dc:date>2009-10-01T13:07:57Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Best hardware solution for moving our envoirnment to VM</title>
      <link>http://communities.vmware.com/message/1378771</link>
      <description>&lt;br /&gt;
Ok sou you can have 2 QUadCOre CPU with e.g. 32 GB RAM with an RAID1 with two SAS Drives, if you want to use ESX4.&lt;br /&gt;
&lt;p /&gt;
If you want to use ESXi you can alos take an USB as the boot Device.&lt;br /&gt;
&lt;p /&gt;
But you hardware should be supported by vmware.&lt;br /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/resources/compatibility/search.php?source=hp&amp;#38;q=vmware%20hcl&amp;#38;meta=&amp;#38;aq=0&amp;#38;oq="&gt;http://www.vmware.com/resources/compatibility/search.php?source=hp&amp;#38;q=vmware%20hcl&amp;#38;meta=&amp;#38;aq=0&amp;#38;oq=&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
MCP, VCP</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">3.5</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">analysis</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">bestpractice</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">cpu</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">disk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx3.5</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxtop</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">iscsi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">kernel</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">linux</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">memory</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">network</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">nfs</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance_issues</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">san</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">scheduling</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">slow</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">smp</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">storage</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">virtualcenter</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vmfs</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">windows</category>
      <pubDate>Thu, 01 Oct 2009 11:21:05 GMT</pubDate>
      <author>krowczynski</author>
      <guid>http://communities.vmware.com/message/1378771</guid>
      <dc:date>2009-10-01T11:21:05Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>VM with W2003 64bits &amp;#38; 4GB of RAM showing less (3.75GB)</title>
      <link>http://communities.vmware.com/message/1378510</link>
      <description>&lt;br /&gt;
This is most likely due to RAM reservation for virtual PCI devices. PCI devices need memory for their IO and those pages are not available to the OS. Hence the gap that you see...</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vm</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">2003</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">64bits</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">less</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">memory</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">than</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">installed</category>
      <pubDate>Thu, 01 Oct 2009 01:41:47 GMT</pubDate>
      <author>avasudevan</author>
      <guid>http://communities.vmware.com/message/1378510</guid>
      <dc:date>2009-10-01T01:41:47Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Capacity Planning and scaling with over subscription in mind..</title>
      <link>http://communities.vmware.com/message/1378227</link>
      <description>However, if a given VM spikes demand for memory, beyond expectation, so the balloon process is pinched, or worse VMs are allocated memory beyond physical memory and physical memory is exceeded by demand requests, ESX host will page to disk via the swap configuration, and then every single VM, regardless of or if they requested memory will be impacted because writting to swap is painful to performance. WIth memory so inexpensive and many if not all servers running lots of RAM for virtualization, any overcommitment of memory should be avoided. Best practice is to not over subscribe memory unless you really know when and how applications in VM memory demand trends proceed.  Memory overcommitment can lead to network or disk IO overcommitment beyond typical peak scaling.  I have seen ESX hosts chase their respective tails trying to perform when memory oversubscription leads to network and/or disk IO additional over subscription... all because some PM or purchasing resource did not want to spend on relatively inexpensive RAM?  The first thing I encourse clients to do... is increase RAM when an ESX host is struggling with this issue.  You would be surprised with the results!</description>
      <pubDate>Wed, 30 Sep 2009 18:57:41 GMT</pubDate>
      <author>Schorschi</author>
      <guid>http://communities.vmware.com/message/1378227</guid>
      <dc:date>2009-09-30T18:57:41Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Virtual machines poor performance after idle time.</title>
      <link>http://communities.vmware.com/message/1377770</link>
      <description>Have you checked to make sure the vm's power settings are correct? No standby, no hard disk power management etc?? If the hard disks are set to turn off after a certain time that can cause this, same with any processor or system power management settings.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">virtual</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">machines</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">idle</category>
      <pubDate>Wed, 30 Sep 2009 12:11:45 GMT</pubDate>
      <author>s1xth</author>
      <guid>http://communities.vmware.com/message/1377770</guid>
      <dc:date>2009-09-30T12:11:45Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Linux VM, rsync throughput question</title>
      <link>http://communities.vmware.com/message/1377352</link>
      <description>Hiya&lt;br /&gt;
&lt;br /&gt;
Thanks for that.  &lt;br /&gt;
&lt;p /&gt;
Finally got to the bottom of this :&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
The Host has 8GB of memory.&lt;br /&gt;
The VM for what every reason had 16GB of memory allocated.. This is not a problem, as under normal operation it doesn't ever need this. &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
So, when I ran the rsync on the VM, linux kindly allocated 14G  to disk cache to help with rsync.  The HOST doesn't know what the VM is using the memory for, so tried to service the request for the extra memory. Not having the memory, it started to to use SWAP space. This is why rsync ran at full wack for a while and then slowed once it started to use SWAP.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
I only noticed this when the drop in speed seem to coincide with the request fro SWAP.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Solution : I dropped the memory on the VM to 4GB..to stop the host using SWAP,  rsync was happy.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Hope this help&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Kind Regards&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
nomad</description>
      <pubDate>Tue, 29 Sep 2009 23:10:14 GMT</pubDate>
      <author>oznomad</author>
      <guid>http://communities.vmware.com/message/1377352</guid>
      <dc:date>2009-09-29T23:10:14Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>VM CPU issue?</title>
      <link>http://communities.vmware.com/message/1376325</link>
      <description>The uniprocessor HAL is more efficient than the multiprocessor HAL.  If you only have a single vCPU assigned to your VM, you can improve performance slightly by forcing Windows back to the uniprocessor HAL.  You can do this through the device manager and by specifying a driver to the CPU.&lt;br /&gt;
&lt;br /&gt;
The performance difference generally is not great, though.  We have measured it in single digit percentages that are workload dependent.&lt;br /&gt;
&lt;br /&gt;
Scott&lt;br /&gt;
&lt;br /&gt;
More information on my blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://vpivot.com"&gt;http://vpivot.com&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds"&gt;http://twitter.com/drummonds&lt;/a&gt;</description>
      <pubDate>Tue, 29 Sep 2009 02:07:11 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/message/1376325</guid>
      <dc:date>2009-09-29T02:07:11Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>XP guest slows down when moved to Quad / Vista 64 from XP host</title>
      <link>http://communities.vmware.com/message/1376324</link>
      <description>The only lead I have for you is around Intel's SpeedStep technology.  SpeedStep will increase/decrease the processor frequency based on guest load.  A few months ago I discovered an issue in our hosted products where load inside a VM was not detected by SpeedStep, so the processor ran at very low frequencies.  Check your BIOS and SpeedStep settings (if available) for "max performance" and see if this makes a difference.&lt;br /&gt;
&lt;br /&gt;
Scott&lt;br /&gt;
&lt;br /&gt;
More information on my blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://vpivot.com"&gt;http://vpivot.com&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds"&gt;http://twitter.com/drummonds&lt;/a&gt;</description>
      <pubDate>Tue, 29 Sep 2009 02:04:26 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/message/1376324</guid>
      <dc:date>2009-09-29T02:04:26Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Virtulize SQL on local storage</title>
      <link>http://communities.vmware.com/message/1376323</link>
      <description>The issue here isn't to use ESX or not, but whether you run SQL on the servers available to you.  The overhead of SQL virtualization is so low with ESX 4, and the IO throughput so high, that ESX's presence will be transparent to the application and its users.  You simply must estimate your transaction throughput and subsequent IOPS and assure that your storage can support such a rate.&lt;br /&gt;
&lt;br /&gt;
Scott&lt;br /&gt;
&lt;br /&gt;
More information on my blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://vpivot.com"&gt;http://vpivot.com&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds"&gt;http://twitter.com/drummonds&lt;/a&gt;</description>
      <pubDate>Tue, 29 Sep 2009 01:59:35 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/message/1376323</guid>
      <dc:date>2009-09-29T01:59:35Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Quad core - and 32 bit application</title>
      <link>http://communities.vmware.com/message/1374977</link>
      <description>download and install ESXi, it will give you the ability to assign 4vCPU's to your guest(s) if needed.&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/download/esxi/"&gt;http://www.vmware.com/download/esxi/&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
....but check the VMware &lt;a class="jive-link-external" href="http://www.vmware.com/resources/compatibility/search"&gt;HCL&lt;/a&gt; or the &lt;a class="jive-link-external" href="http://www.vm-help.com//esx40i/esx40_whitebox_HCL.php"&gt;Whitebox HCL&lt;/a&gt;</description>
      <pubDate>Sun, 27 Sep 2009 14:02:38 GMT</pubDate>
      <author>Troy Clavell</author>
      <guid>http://communities.vmware.com/message/1374977</guid>
      <dc:date>2009-09-27T14:02:38Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>vCenter Performance Counters</title>
      <link>http://communities.vmware.com/docs/DOC-5600</link>
      <description>&lt;h1&gt;Introduction&lt;/h1&gt;
The following table of vCenter (VC) performance counters lists the counters with a description of their purpose.  This page has been updated for vSphere 4, so the counter levels will differ slightly on older versions of VC.&lt;br /&gt;
&lt;br /&gt;
Remember, with the exception of ready time, statistic levels one and two are the only ones needed for 99% of the performance monitoring and analysis out there.  Don't spend many of your own cycles worrying about levels three and four!&lt;br /&gt;
&lt;br /&gt;
For information on enabling VC to display and archive these counters see the &lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-5230"&gt;Understanding vCenter Performance Statistics&lt;/a&gt; article.&lt;br /&gt;
&lt;br /&gt;
&lt;h1&gt;Understanding vCenter Measurement Windows&lt;/h1&gt;
Before you continue, you should know that all total count metrics reported by VC are reported over the sample window.  When you're looking at live stats, this sample window is 20 seconds.  When you're looking at archive stats, it will depend on the interval duration.  That duration could be five minutes, 30 minutes, two hours, or one day.&lt;br /&gt;
&lt;br /&gt;
This causes a lot of confusion when comparing esxtop results to live VC results to archived VC results.  As an example, ready time might be reported as 10% in esxtop.  In live VC results this amount of ready time would be reported as 2000 ms (10% of the 20s window.)  In one day archive results, the same number would be reported as 30,000 ms (10% of the five minute interval duration.)  All of these numbes reflect the same amount of ready time.&lt;br /&gt;
&lt;br /&gt;
&lt;h1&gt;CPU Statistics&lt;/h1&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;Level&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Counter name in API&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Description&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Units&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;cpu.ready.summation&lt;/td&gt;
&lt;td&gt;Ready time is the time spend waiting for CPU(s) to become available in the past update interval.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;cpu.usagemhz.average&lt;/td&gt;
&lt;td&gt;The CPU utilization.  The maximum possible value here is the frequency of the processors times the number of cores.  As an example, a VM using 4000 MHz  on a system with four 2 GHz processors is using 50% of the CPU (4000 / (4 * 2000) = 0.5)&lt;/td&gt;
&lt;td&gt;megaHertz&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;cpu.usage.average&lt;/td&gt;
&lt;td&gt;The CPU utilization.  This value is reported with 100% representing all processor cores on the system.  As an example, a 2-way VM using 50% of a four-core system is completely using two cores.&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;cpu.reservedCapacity.average&lt;/td&gt;
&lt;td&gt;CPU Reserved Capacity&lt;/td&gt;
&lt;td&gt;megaHertz&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;cpu.idle.summation&lt;/td&gt;
&lt;td&gt;CPU Idle&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;cpu.swapwait.summation&lt;/td&gt;
&lt;td&gt;Swap wait time is time that the world spent waiting for memory to be swapped in.  When the VM is waiting for memory, it is not doing work.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;cpu.system.summation&lt;/td&gt;
&lt;td&gt;System time is the time spent in VMkernel during the last update interval.  This does not include guest code execution.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;cpu.wait.summation&lt;/td&gt;
&lt;td&gt;Wait time is the time spent waiting for hardware or VMkernel lock thread locks during the last update interval.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;cpu.extra.summation&lt;/td&gt;
&lt;td&gt;CPU extra is the time above the statically calculated entitlement. Entitlement is the share of processing time that a VM should get as a result of its vCPU count and assigned shares. &lt;i&gt;You should not use or care about this counter in any of your own analysis.&lt;/i&gt;&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;cpu.used.summation&lt;/td&gt;
&lt;td&gt;CPU Used&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;cpu.guaranteed.latest&lt;/td&gt;
&lt;td&gt;Guaranteed time is reported as the amount of the reservation time that the VM used in the past update interval.  As an example, if 2000 MHz have been reserved for the VM on an four-way, 2 GHz host, that's 25% of the CPU resource.  In a 20s update interval, there are 80,000 ms available on this four-way system.  That means 20,000 ms of time has been reserved.  If a VM used only half of its available cycles, the guaranteed time is 10,000 ms.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;cpu.usage.none&lt;/td&gt;
&lt;td&gt;CPU Usage (None)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;cpu.usage.minimum&lt;/td&gt;
&lt;td&gt;CPU Usage (Minimum)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;cpu.usage.maximum&lt;/td&gt;
&lt;td&gt;CPU Usage (Maximum)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;cpu.usagemhz.none&lt;/td&gt;
&lt;td&gt;CPU Usage in MHz (None)&lt;/td&gt;
&lt;td&gt;megaHertz&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;cpu.usagemhz.minimum&lt;/td&gt;
&lt;td&gt;CPU Usage in MHz (Minimum)&lt;/td&gt;
&lt;td&gt;megaHertz&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;cpu.usagemhz.maximum&lt;/td&gt;
&lt;td&gt;CPU Usage in MHz (Maximum)&lt;/td&gt;
&lt;td&gt;megaHertz&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;
&lt;br /&gt;
&lt;h1&gt;Memory Statistics&lt;/h1&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;Level&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Counter name in API&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Description&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;units&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;mem.consumed.average&lt;/td&gt;
&lt;td&gt;The amount of machine memory that is in use by the VM. While a VM may&lt;br /&gt;
			have been configured to use 4 GB of RAM, as an example, it might have&lt;br /&gt;
			only touched half of that. Of the 2 GB left, half of that might be&lt;br /&gt;
			saved from memory sharing. That would result in 1 GB of consumed memory.&lt;br /&gt;&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;mem.overhead.average&lt;/td&gt;
&lt;td&gt;The memory used by the VMkernel to maintain and execute the VM.&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;mem.swapinrate.average&lt;/td&gt;
&lt;td&gt;The swap in rate reports the rate at which a VM's memory is being swapped in from disk.&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;mem.swapoutrate.average&lt;/td&gt;
&lt;td&gt;The swap out rate reports the rate at which a VM's memory is being swapped out to disk.&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;mem.usage.average&lt;/td&gt;
&lt;td&gt;The percentage of memory used as a percent of all available machine memory.  Available for host and VM.&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;mem.vmmemctl.average&lt;/td&gt;
&lt;td&gt;The amount of memory currently claimed by the balloon driver. This is&lt;br /&gt;
			not a performance problem, per se, but represents the host starting to&lt;br /&gt;
			take memory from less needful VMs for those with large amounts of&lt;br /&gt;
			active memory. But if the host is ballooning, check swap rates (swapin&lt;br /&gt;
			and swapout) which would be indicative of performance problems.&lt;br /&gt;&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.granted.average&lt;/td&gt;
&lt;td&gt;The amount of memory that was granted to the VM by the host.  Memory is not granted to the host until it is touched one time and granted memory may be swapped out or ballooned away if the VMkernel needs the memory.&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.active.average&lt;/td&gt;
&lt;td&gt;The amount of memory used by the VM in the past small window of time.  This is the "true" number of how much memory the VM currently has need of.  Additional, unused memory may be swapped out or ballooned with no impact to the guest's performance.&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.shared.average&lt;/td&gt;
&lt;td&gt;The average amount of shared memory.  Shared memory represents the entire pool of memory from which sharing savings are possible.  The amount of memory that this has been condensed to is reported in shared common memory.  So, total saving due to memory sharing equals shared memory minus shared common memory.&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.zero.average&lt;/td&gt;
&lt;td&gt;The amount of zero pages in the guest.  Zero pages are not represented in machine memory so this results in 100% savings when mapping from the guest to the machine memory.&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.unreserved.average&lt;/td&gt;
&lt;td&gt;Memory Unreserved (Average)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.swapused.average&lt;/td&gt;
&lt;td&gt;The amount of swap memory currently in use.  A large amount of swap memory is not a performance problem.  This could be memory that the guest doesn't need.  Check the swap rates (swapin, swapout) to see if the guest is actively in need of more memory than is available.&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.swapunreserved.average&lt;/td&gt;
&lt;td&gt;Memory Swap Unreserved (Average)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.sharedcommon.average&lt;/td&gt;
&lt;td&gt;The average amount of shared common memory.  Shared memory represents the entire pool of memory from which sharing savings are possible.  The amount of memory that this has been condensed to is reported in shared common memory.  So, total saving due to memory sharing equals shared memory minus shared common memory.&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.heap.average&lt;/td&gt;
&lt;td&gt;Memory Heap (Average)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.heapfree.average&lt;/td&gt;
&lt;td&gt;Memory Heap Free (Average)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.state.latest&lt;/td&gt;
&lt;td&gt;Memory State&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.swapped.average&lt;/td&gt;
&lt;td&gt;Memory Swapped (Average)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.swaptarget.average&lt;/td&gt;
&lt;td&gt;Memory Swap Target (Average)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.swapin.average&lt;/td&gt;
&lt;td&gt;The rate at which memory is being swapped in from disk.  A large number here represents a problem with lack of memory and a clear indication that performance is suffering as a result.&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.swapout.average&lt;/td&gt;
&lt;td&gt;The rate at which memory is being swapped out to disk.  A large number here represents a problem with lack of memory and a clear indication that performance is suffering as a result.&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.vmmemctltarget.average&lt;/td&gt;
&lt;td&gt;Memory Balloon Target (Average)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.sysUsage.average&lt;/td&gt;
&lt;td&gt;Memory Used by vmkernel&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;mem.reservedCapacity.average&lt;/td&gt;
&lt;td&gt;Memory Reserved Capacity&lt;/td&gt;
&lt;td&gt;megaBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.usage.none&lt;/td&gt;
&lt;td&gt;Memory Usage (None)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.usage.minimum&lt;/td&gt;
&lt;td&gt;Memory Usage (Minimum)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.usage.maximum&lt;/td&gt;
&lt;td&gt;Memory Usage (Maximum)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.granted.none&lt;/td&gt;
&lt;td&gt;Memory Granted (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.granted.minimum&lt;/td&gt;
&lt;td&gt;Memory Granted (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.granted.maximum&lt;/td&gt;
&lt;td&gt;Memory Granted (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.active.none&lt;/td&gt;
&lt;td&gt;Memory Active (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.active.minimum&lt;/td&gt;
&lt;td&gt;Memory Active (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.active.maximum&lt;/td&gt;
&lt;td&gt;Memory Active (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.shared.none&lt;/td&gt;
&lt;td&gt;Memory Shared (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.shared.minimum&lt;/td&gt;
&lt;td&gt;Memory Shared (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.shared.maximum&lt;/td&gt;
&lt;td&gt;Memory Shared (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.zero.none&lt;/td&gt;
&lt;td&gt;Memory Zero (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.zero.minimum&lt;/td&gt;
&lt;td&gt;Memory Zero (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.zero.maximum&lt;/td&gt;
&lt;td&gt;Memory Zero (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.unreserved.none&lt;/td&gt;
&lt;td&gt;Memory Unreserved (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.unreserved.minimum&lt;/td&gt;
&lt;td&gt;Memory Unreserved (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.unreserved.maximum&lt;/td&gt;
&lt;td&gt;Memory Unreserved (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapused.none&lt;/td&gt;
&lt;td&gt;Memory Swap Used (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapused.minimum&lt;/td&gt;
&lt;td&gt;Memory Swap Used (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapused.maximum&lt;/td&gt;
&lt;td&gt;Memory Swap Used (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapunreserved.none&lt;/td&gt;
&lt;td&gt;Memory Swap Unreserved (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapunreserved.minimum&lt;/td&gt;
&lt;td&gt;Memory Swap Unreserved (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapunreserved.maximum&lt;/td&gt;
&lt;td&gt;Memory Swap Unreserved (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.sharedcommon.none&lt;/td&gt;
&lt;td&gt;Memory Shared Common (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.sharedcommon.minimum&lt;/td&gt;
&lt;td&gt;Memory Shared Common (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.sharedcommon.maximum&lt;/td&gt;
&lt;td&gt;Memory Shared Common (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.heap.none&lt;/td&gt;
&lt;td&gt;Memory Heap (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.heap.minimum&lt;/td&gt;
&lt;td&gt;Memory Heap (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.heap.maximum&lt;/td&gt;
&lt;td&gt;Memory Heap (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.heapfree.none&lt;/td&gt;
&lt;td&gt;Memory Heap Free (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.heapfree.minimum&lt;/td&gt;
&lt;td&gt;Memory Heap Free (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.heapfree.maximum&lt;/td&gt;
&lt;td&gt;Memory Heap Free (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapped.none&lt;/td&gt;
&lt;td&gt;Memory Swapped (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapped.minimum&lt;/td&gt;
&lt;td&gt;Memory Swapped (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapped.maximum&lt;/td&gt;
&lt;td&gt;Memory Swapped (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swaptarget.none&lt;/td&gt;
&lt;td&gt;Memory Swap Target (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swaptarget.minimum&lt;/td&gt;
&lt;td&gt;Memory Swap Target (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swaptarget.maximum&lt;/td&gt;
&lt;td&gt;Memory Swap Target (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapin.none&lt;/td&gt;
&lt;td&gt;Memory Swap In (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapin.minimum&lt;/td&gt;
&lt;td&gt;Memory Swap In (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapin.maximum&lt;/td&gt;
&lt;td&gt;Memory Swap In (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapout.none&lt;/td&gt;
&lt;td&gt;Memory Swap Out (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapout.minimum&lt;/td&gt;
&lt;td&gt;Memory Swap Out (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.swapout.maximum&lt;/td&gt;
&lt;td&gt;Memory Swap Out (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.vmmemctl.none&lt;/td&gt;
&lt;td&gt;Memory Balloon (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.vmmemctl.minimum&lt;/td&gt;
&lt;td&gt;Memory Balloon (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.vmmemctl.maximum&lt;/td&gt;
&lt;td&gt;Memory Balloon (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.vmmemctltarget.none&lt;/td&gt;
&lt;td&gt;Memory Balloon Target (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.vmmemctltarget.minimum&lt;/td&gt;
&lt;td&gt;Memory Balloon Target (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.vmmemctltarget.maximum&lt;/td&gt;
&lt;td&gt;Memory Balloon Target (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.overhead.none&lt;/td&gt;
&lt;td&gt;Memory Overhead (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.overhead.minimum&lt;/td&gt;
&lt;td&gt;Memory Overhead (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.overhead.maximum&lt;/td&gt;
&lt;td&gt;Memory Overhead (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.consumed.none&lt;/td&gt;
&lt;td&gt;Memory Consumed (None)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.consumed.maximum&lt;/td&gt;
&lt;td&gt;Memory Consumed (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.consumed.minimum&lt;/td&gt;
&lt;td&gt;Memory Consumed (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.sysUsage.none&lt;/td&gt;
&lt;td&gt;Memory Used by vmkernel&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.sysUsage.maximum&lt;/td&gt;
&lt;td&gt;Memory Used by vmkernel&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;mem.sysUsage.minimum&lt;/td&gt;
&lt;td&gt;Memory Used by vmkernel&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;
&lt;br /&gt;
&lt;h1&gt;Disk Statistics&lt;/h1&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;Level&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Counter name in API&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Description&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;units&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;disk.maxTotalLatency&lt;/td&gt;
&lt;td&gt;The highest reported total latency (device and kernel times) in the sample window.&lt;/td&gt;
&lt;td&gt;milliseconds&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;disk.usage.average&lt;/td&gt;
&lt;td&gt;Average disk throughput over the sample period.&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.read.average&lt;/td&gt;
&lt;td&gt;Average disk throughput due to read operaitons over the sample period.&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.write.average&lt;/td&gt;
&lt;td&gt;Average disk throughput due to write operations over the sample period.&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.commands.summation&lt;/td&gt;
&lt;td&gt;Disk Commands Issued&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.commandsAborted.summation&lt;/td&gt;
&lt;td&gt;The number of aborts that have occurred in the last window of time. Abort commands are issued by the guest when the storage system has not responded within an acceptable amount of time (as defined by the guest OS or application.)&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.busResets.summation&lt;/td&gt;
&lt;td&gt;Disk Bus Resets&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.deviceReadLatency.average&lt;/td&gt;
&lt;td&gt;Device read latency.  This is the time the physical device from the HBA to the platter takes to service an IO request.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.kernelReadLatency.average&lt;/td&gt;
&lt;td&gt;Kernel read latency.  This is the time the VMkernel takes to service an IO.  This is the time between the guest OS and the device.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.totalReadLatency.average&lt;/td&gt;
&lt;td&gt;Total read latency.  The sum of the device and kernel read latencies.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.queueReadLatency.average&lt;/td&gt;
&lt;td&gt;Queue Read Latency&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.deviceWriteLatency.average&lt;/td&gt;
&lt;td&gt;Device write latency. This is the time the physical device from the HBA to the platter takes to service an IO request.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.kernelWriteLatency.average&lt;/td&gt;
&lt;td&gt;Kernel write latency.  This is the time the VMkernel takes to service an IO.  This is the time between the guest OS and the device.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.totalWriteLatency.average&lt;/td&gt;
&lt;td&gt;Total write latency.  The sum of the device and kernel write latencies.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.queueWriteLatency.average&lt;/td&gt;
&lt;td&gt;Queue Write Latency&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.deviceLatency.average&lt;/td&gt;
&lt;td&gt;Physical Device Command Latency&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.kernelLatency.average&lt;/td&gt;
&lt;td&gt;Kernel Disk Command Latency&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;disk.queueLatency.average&lt;/td&gt;
&lt;td&gt;Queue Command Latency&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;disk.numberRead.summation&lt;/td&gt;
&lt;td&gt;The number of IO read operations in the previous sample period.  Note that these operations may be variable sized up to 64 KB.&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;disk.numberWrite.summation&lt;/td&gt;
&lt;td&gt;The number of IO write operations in the previous sample period.  Note that these operations may be variable sized up to 64 KB.&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;disk.totalLatency.average&lt;/td&gt;
&lt;td&gt;This is the average total latency over the sample window.  Total latency is the sum of kernel and device latency for both read and write commands.&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;disk.write.average&lt;/td&gt;
&lt;td&gt;Disk Write Rate&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;disk.usage.none&lt;/td&gt;
&lt;td&gt;Disk Usage (None)&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;disk.usage.minimum&lt;/td&gt;
&lt;td&gt;Disk Usage (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;disk.usage.maximum&lt;/td&gt;
&lt;td&gt;Disk Usage (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;
&lt;br /&gt;
&lt;h1&gt;Network Statistics&lt;/h1&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;Level&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Counter name in API&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Description&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;units&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;net.usage.average&lt;/td&gt;
&lt;td&gt;Network Usage (Average)&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;net.droppedRx.summation&lt;/td&gt;
&lt;td&gt;The number of received packets that were dropped over the sample period.&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;net.droppedTx.summation&lt;/td&gt;
&lt;td&gt;The number of transmitted packets that were dropped over the sample period.&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;net.received.average&lt;/td&gt;
&lt;td&gt;Average network throughput for received traffic.&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;net.transmitted.average&lt;/td&gt;
&lt;td&gt;Average network throughput for transmitted traffic.&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;net.packetsRx.summation&lt;/td&gt;
&lt;td&gt;Network Packets Received&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;net.packetsTx.summation&lt;/td&gt;
&lt;td&gt;Network Packets Transmitted&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;net.usage.none&lt;/td&gt;
&lt;td&gt;Network Usage (None)&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;net.usage.minimum&lt;/td&gt;
&lt;td&gt;Network Usage (Minimum)&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;net.usage.maximum&lt;/td&gt;
&lt;td&gt;Network Usage (Maximum)&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;
&lt;br /&gt;
&lt;h1&gt;Other Statistics&lt;/h1&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;&lt;b&gt;Level&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Counter name in API&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;Description&lt;/b&gt;&lt;/td&gt;
&lt;td&gt;&lt;b&gt;units&lt;/b&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;sys.uptime.latest&lt;/td&gt;
&lt;td&gt;Uptime&lt;/td&gt;
&lt;td&gt;second&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;sys.heartbeat.summation&lt;/td&gt;
&lt;td&gt;Heartbeat&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;clusterServices.cpufairness.latest&lt;/td&gt;
&lt;td&gt;CPU Fairness&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;clusterServices.memfairness.latest&lt;/td&gt;
&lt;td&gt;Memory Fairness&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;clusterServices.effectivecpu.average&lt;/td&gt;
&lt;td&gt;Effective CPU Resources&lt;/td&gt;
&lt;td&gt;megaHertz&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;clusterServices.effectivemem.average&lt;/td&gt;
&lt;td&gt;Effective Memory Resources&lt;/td&gt;
&lt;td&gt;megaBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;clusterServices.failover.latest&lt;/td&gt;
&lt;td&gt;Current failover level&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;sys.resourceCpuUsage.average&lt;/td&gt;
&lt;td&gt;Resource CPU Usage (Average)&lt;/td&gt;
&lt;td&gt;megaHertz&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;managementAgent.memUsed.average&lt;/td&gt;
&lt;td&gt;Memory Used (Average)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;managementAgent.swapUsed.average&lt;/td&gt;
&lt;td&gt;Memory Swap Used (Average)&lt;/td&gt;
&lt;td&gt;kiloBytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;managementAgent.swapIn.average&lt;/td&gt;
&lt;td&gt;Memory Swap In (Average)&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;managementAgent.swapOut.average&lt;/td&gt;
&lt;td&gt;Memory Swap Out (Average)&lt;/td&gt;
&lt;td&gt;kiloBytesPerSecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.actav1.latest&lt;/td&gt;
&lt;td&gt;CPU Active (1 min. average)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.actpk1.latest&lt;/td&gt;
&lt;td&gt;CPU Active (1 min. peak)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.runav1.latest&lt;/td&gt;
&lt;td&gt;CPU Running (1 min. average)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.actav5.latest&lt;/td&gt;
&lt;td&gt;CPU Active (5 min. average)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.actpk5.latest&lt;/td&gt;
&lt;td&gt;CPU Active (5 min. peak)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.runav5.latest&lt;/td&gt;
&lt;td&gt;CPU Running (5 min. average)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.actav15.latest&lt;/td&gt;
&lt;td&gt;CPU Active (15 min. average)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.actpk15.latest&lt;/td&gt;
&lt;td&gt;CPU Active (15 min. peak)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.runav15.latest&lt;/td&gt;
&lt;td&gt;CPU Running (15 min. average)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.runpk1.latest&lt;/td&gt;
&lt;td&gt;CPU Running (1 min. peak)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.maxLimited1.latest&lt;/td&gt;
&lt;td&gt;CPU Throttled (1 min. average)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.runpk5.latest&lt;/td&gt;
&lt;td&gt;CPU Running (5 min. peak)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.maxLimited5.latest&lt;/td&gt;
&lt;td&gt;CPU Throttled (5 min. average)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.runpk15.latest&lt;/td&gt;
&lt;td&gt;CPU Running (15 min. peak)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.maxLimited15.latest&lt;/td&gt;
&lt;td&gt;CPU Throttled (15 min. average)&lt;/td&gt;
&lt;td&gt;percent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.sampleCount.latest&lt;/td&gt;
&lt;td&gt;Group CPU Sample Count&lt;/td&gt;
&lt;td&gt;number&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;rescpu.samplePeriod.latest&lt;/td&gt;
&lt;td&gt;Group CPU Sample Period&lt;/td&gt;
&lt;td&gt;millisecond&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;sys.resourceCpuUsage.none&lt;/td&gt;
&lt;td&gt;Resource CPU Usage (None)&lt;/td&gt;
&lt;td&gt;megaHertz&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;sys.resourceCpuUsage.maximum&lt;/td&gt;
&lt;td&gt;Resource CPU Usage (Maximum)&lt;/td&gt;
&lt;td&gt;megaHertz&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;sys.resourceCpuUsage.minimum&lt;/td&gt;
&lt;td&gt;Resource CPU Usage (Minimum)&lt;/td&gt;
&lt;td&gt;megaHertz&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">analysis</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">cpu</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">disk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">memory</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">network</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">storage</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">virtualcenter</category>
      <pubDate>Fri, 30 May 2008 00:15:21 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/docs/DOC-5600</guid>
      <dc:date>2008-05-30T00:15:21Z</dc:date>
      <clearspace:dateToText>1 month, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Packet loss on Sun Fire X4140 / ESXi 3.5u4</title>
      <link>http://communities.vmware.com/message/1373306</link>
      <description>&lt;br /&gt;
No, I couldn't make much progress. Just to be clear, the NICs were functional and my observations were related to packet loss at high throughputs.&lt;br /&gt;
&lt;p /&gt;
I had the SunFire under an eval program, so I had to return it. I'm now using an IBM x3550M2 and am not seeing this. Have also upgraded to ESXi4.0 and am using VmxNet drivers on the interfaces.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">network</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">packet_loss</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxi_3.5</category>
      <pubDate>Thu, 24 Sep 2009 19:18:20 GMT</pubDate>
      <author>HMVM123</author>
      <guid>http://communities.vmware.com/message/1373306</guid>
      <dc:date>2009-09-24T19:18:20Z</dc:date>
      <clearspace:dateToText>1 month, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>SQl server performance down after migration from P to V..now we have allocated 6 GB ram and 4vCPU and 3 GB reserverd RAM but no improvement..its taking double time for mdf data copying in copriason with P</title>
      <link>http://communities.vmware.com/message/1372119</link>
      <description>How much RAM is in the ESX Host?  How many CPU cores are in the host?  How many other VM's are on that host?  What kind of disk is the VM on, SATA, SAS, FC?&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Charles Killmer, VCP&lt;br /&gt;
&lt;br /&gt;
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">analysis</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance_issues</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">san</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">storage</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">windows</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">slow</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx3.5</category>
      <pubDate>Wed, 23 Sep 2009 18:12:43 GMT</pubDate>
      <author>Chuck8773</author>
      <guid>http://communities.vmware.com/message/1372119</guid>
      <dc:date>2009-09-23T18:12:43Z</dc:date>
      <clearspace:dateToText>2 months, 22 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Virtual Machine Swap file location</title>
      <link>http://communities.vmware.com/message/1371245</link>
      <description>Another good reason for centalising your Swap is so that you can remove it from a backup strategy.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points&lt;br /&gt;
&lt;br /&gt;
Tom Howarth VCP / vExpert&lt;br /&gt;
VMware Communities User Moderator&lt;br /&gt;
Blog: &lt;a class="jive-link-external" href="http://www.planetvm.net/"&gt;www.planetvm.net&lt;/a&gt;&lt;br /&gt;
Contributing author for the upcoming book "&lt;a class="jive-link-external" href="http://my.safaribooksonline.com/9780136083214"&gt;VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment&lt;/a&gt;&amp;rdquo;. Currently available on roughcuts</description>
      <pubDate>Tue, 22 Sep 2009 21:24:26 GMT</pubDate>
      <author>tom howarth</author>
      <guid>http://communities.vmware.com/message/1371245</guid>
      <dc:date>2009-09-22T21:24:26Z</dc:date>
      <clearspace:dateToText>2 months, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Memory Allocation Alert raised yet VM is well below 50%. VC is reporting wrong</title>
      <link>http://communities.vmware.com/message/1370537</link>
      <description>Thanks ... that explains it.. its a general problem. Hope they fix it soon because alerts are useless like this.</description>
      <pubDate>Tue, 22 Sep 2009 13:09:32 GMT</pubDate>
      <author>armaniseal</author>
      <guid>http://communities.vmware.com/message/1370537</guid>
      <dc:date>2009-09-22T13:09:32Z</dc:date>
      <clearspace:dateToText>2 months, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>VMware ESX 3.02, c-Class Enclosures &amp;#38; HP EVA 8x00</title>
      <link>http://communities.vmware.com/message/1369716</link>
      <description>&lt;br /&gt;
Hello,&lt;br /&gt;
&lt;p /&gt;
 Im hoping someone will be able to assist me with regards to read and write latency.&lt;br /&gt;
&lt;p /&gt;
 I have been doing some baseline storage reports for the EXA's that host our VMware Virtual Desktop Infrastructure.&lt;br /&gt;
&lt;p /&gt;
The setup I have is HP c-Class enclosures running VMware. 2 x 8 Server clusters per enclosure. Connectivity and Server hardware are BL485 G5 Servers - HBA - mds9124e internal - mds9124e external - (NPV mode) - Core Switch - Storage Port (EVA) - EVA 8100.&lt;br /&gt;
&lt;p /&gt;
Load is evenly distributed across all storage processor ports which the Controller Status Performance Object is showing. 1 controller is working slightly more as the BFS volumes all go through Port 1 on Controller A due to the installation LUN must be the lowest-numbered of the LUNs available to the physical host.&lt;br /&gt;
&lt;p /&gt;
Do we have any figures as to limitations on the following EVAPerf counters?&lt;br /&gt;
&lt;p /&gt;
Host Port Statistics Performance Object &lt;br /&gt;
Read Req/s  &amp;#38; Write Req/s &lt;br /&gt;
Read MB/s &amp;#38; Write MB/s &lt;br /&gt;
Read Latency &amp;#38; Write Latency&lt;br /&gt;
Av Queue Depth &lt;br /&gt;
&lt;p /&gt;
 Queue Depth Readings are around 1-2 which looks to be fine, host port Stats look to be fine with utilization on the paired controllers below 50%&lt;br /&gt;
&lt;p /&gt;
The issue where I need assistance is the Average Read Latency &amp;#38; Average Write Latency, I understand that Aa average Read Latency &amp;lt; 15ms and Average Write Latency &amp;lt; 5 ms should be acceptable for most workloads, does this also cound for VDI's?&lt;br /&gt;
&lt;p /&gt;
I am seeing the readings below, read latency is fine, however the write latency is above the 5 (ms) recomendation, now this recomendation isnt set in stone and so if there are any concrete acceptable / not acceptable figures out there supplied by HP or VMware I would appreashiate a benchmark figure.&lt;br /&gt;
&lt;p /&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;Totals&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;Average Read Latency (ms)&lt;/td&gt;
&lt;td&gt;Average Write Latency (ms)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DATA_DG1&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;9.117820069&lt;/td&gt;
&lt;td&gt;8.909515571&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;DATA_DG2&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;9.11710754&lt;/td&gt;
&lt;td&gt;8.340271941&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;
&lt;p /&gt;
Kind Regrads&lt;br /&gt;
&lt;p /&gt;
 Deano</description>
      <pubDate>Mon, 21 Sep 2009 19:32:07 GMT</pubDate>
      <author>VCP210708</author>
      <guid>http://communities.vmware.com/message/1369716</guid>
      <dc:date>2009-09-21T19:32:07Z</dc:date>
      <clearspace:dateToText>2 months, 2 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Java Performance on VMware ESX</title>
      <link>http://communities.vmware.com/message/1367585</link>
      <description>Having gone through those best practices, yes, we're on board with all of them.&lt;br /&gt;
&lt;br /&gt;
The only variable we have here is the 'hardware' platform on which the tomcat java service is running.  The software is on an NFS server, so both physical and virtual servers are getting their tomcat copy from the same place.  The same goes for the Oracle client software.  The Oracle server is on a physical machine, and is the same for both the physical and virtual clients.  The OS installed on the physical and virtual machines is also identical, with the exception of some of the device driver modules in use, a natural consequence of virtualising the system.&lt;br /&gt;
&lt;br /&gt;
So we have already controlled for most variables.  I'm still waiting for the broken-down code snippets from the users.&lt;br /&gt;
&lt;br /&gt;
Tim</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">java</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <pubDate>Fri, 18 Sep 2009 14:45:27 GMT</pubDate>
      <author>tcutts</author>
      <guid>http://communities.vmware.com/message/1367585</guid>
      <dc:date>2009-09-18T14:45:27Z</dc:date>
      <clearspace:dateToText>2 months, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>22</clearspace:replyCount>
    </item>
    <item>
      <title>Reservations??  resource priorites??</title>
      <link>http://communities.vmware.com/message/1368548</link>
      <description>Thanks much.    You comments were very helpful.</description>
      <pubDate>Sun, 20 Sep 2009 13:09:07 GMT</pubDate>
      <author>wade001</author>
      <guid>http://communities.vmware.com/message/1368548</guid>
      <dc:date>2009-09-20T13:09:07Z</dc:date>
      <clearspace:dateToText>2 months, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>IBM x3850 M2 VM performance issues?</title>
      <link>http://communities.vmware.com/message/1368258</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
There's a similar issue faced by me in one of my deployments. Even after upgrading to the latest BMC Update given by IBM on its site for &lt;br /&gt;
&lt;p /&gt;
X3850 M2  has not given us positive results. &lt;br /&gt;
&lt;p /&gt;
The issue is specifically with I/O intensive Servers like Citrix Xe App 4.5 where it touches 100 % CPU after having 15-20 Users. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Sat, 19 Sep 2009 13:38:18 GMT</pubDate>
      <author>vikrams04</author>
      <guid>http://communities.vmware.com/message/1368258</guid>
      <dc:date>2009-09-19T13:38:18Z</dc:date>
      <clearspace:dateToText>2 months, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>Insufficient system resources when running multiple vm</title>
      <link>http://communities.vmware.com/message/1367738</link>
      <description>I am going to assume that when you say "images" you are referring to virtual machines.&lt;br /&gt;
&lt;br /&gt;
ESX (indeed, all of our virtualization products) provide hardened, isolated virtual machines that are not aware of anything else happening on the system.  So, no matter how many VMs you instantiate, the guest OSes in each will not be aware of memory pressure in the host.&lt;br /&gt;
&lt;br /&gt;
There is one exception to this: once memory has been over-committed the balloon driver will inflate inside the guest, pinning memory, and prohibiting the guest OS and its applications from using that memory.  This could explain what you are seeing.  But, since the balloon driver's maximum size is limited to 65% of the VM's size, balloon inflation should not cause guest OS or application crashes like you describe. &lt;br /&gt;
&lt;br /&gt;
Scott&lt;br /&gt;
&lt;br /&gt;
More information on my blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://vpivot.com"&gt;http://vpivot.com&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds"&gt;http://twitter.com/drummonds&lt;/a&gt;</description>
      <pubDate>Fri, 18 Sep 2009 16:59:30 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/message/1367738</guid>
      <dc:date>2009-09-18T16:59:30Z</dc:date>
      <clearspace:dateToText>2 months, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Help to understand how to monitord esx with third part tool</title>
      <link>http://communities.vmware.com/message/1367735</link>
      <description>I do not have any experience with third-party tools but I know that they are dependent on the SDK, which provides access to the same counters that vCenter uses.  I have documented VC's counters (&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-5600"&gt;vCenter Performance Counters&lt;/a&gt;) and provided some documentation as to how to use them (&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-3930"&gt;Performance Monitoring and Analysis&lt;/a&gt;).  Try reading those.&lt;br /&gt;
&lt;br /&gt;
Scott&lt;br /&gt;
&lt;br /&gt;
More information on my blog and on Twitter:&lt;br /&gt;
&lt;a class="jive-link-external" href="http://vpivot.com"&gt;http://vpivot.com&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/drummonds"&gt;http://twitter.com/drummonds&lt;/a&gt;</description>
      <pubDate>Fri, 18 Sep 2009 16:45:46 GMT</pubDate>
      <author>drummonds</author>
      <guid>http://communities.vmware.com/message/1367735</guid>
      <dc:date>2009-09-18T16:45:46Z</dc:date>
      <clearspace:dateToText>2 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Performance Troubleshooting for VMware vSphere 4 and ESX 4.0</title>
      <link>http://communities.vmware.com/docs/DOC-10352</link>
      <description>Performance problems can arise in any computing environment. Complex application behaviors, changing demands, and shared infrastructure can lead to problems arising in previously stable environments. Troubleshooting performance problems requires an understanding of the interactions between the software and hardware components of a computing environment. Moving to a virtualized computing environment adds new software layers and new types of interactions that must be considered when troubleshooting performance problems. &lt;br /&gt;
&lt;br /&gt;
The attached document is the first installment in a guide covering performance troubleshooting in a vSphere environment. It uses a guided approach to lead the reader through the observable manifestations of complex hardware/software interactions in order to identify specific performance problems. For each problem covered, it includes a discussion of the possible root-causes and solutions. Topics covered include performance problems arising from issues in the CPU, memory, storage, and network subsystems, as well as in the VM and ESX host configuration.  Guidance is given on relevant performance metrics to observe using the vSphere Client and esxtop in order to isolate specific performance issues.  &lt;br /&gt;
&lt;br /&gt;
This first installment of &lt;i&gt;Performance Troubleshooting for VMware vSphere 4&lt;/i&gt; covers performance troubleshooting on a single VMware ESX 4.0 host. It focuses on the most common performance problems which affect an ESX host. Future updates will add more detailed performance information, including troubleshooting information for more advanced problems and multi-host vSphere deployments.&lt;br /&gt;
&lt;br /&gt;
This is a living document. Reader comments, questions, and suggestions are encouraged.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">performance_issues</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">memory</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">cpu</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">disk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">network</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">troubleshooting</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">slow</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">problem</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxtop</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">analysis</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">storage</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">virtualcenter</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esx</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vsphere_performance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">vsphere</category>
      <pubDate>Mon, 13 Jul 2009 14:03:44 GMT</pubDate>
      <author>haroldr</author>
      <guid>http://communities.vmware.com/docs/DOC-10352</guid>
      <dc:date>2009-07-13T14:03:44Z</dc:date>
      <clearspace:dateToText>2 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>how long does the vminstaller take to boot</title>
      <link>http://communities.vmware.com/message/1366865</link>
      <description>&lt;br /&gt;
the cpu's on this server do not support the 64 bit vmware.   I must have confused 3.5 update 4 with esxi 4.0.  so, i'm installing the 3.5 version</description>
      <category domain="http://communities.vmware.com/tags?communityID=2629">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">boot</category>
      <category domain="http://communities.vmware.com/tags?communityID=2629">installable</category>
      <pubDate>Thu, 17 Sep 2009 19:43:05 GMT</pubDate>
      <author>cmlarson</author>
      <guid>http://communities.vmware.com/message/1366865</guid>
      <dc:date>2009-09-17T19:43:05Z</dc:date>
      <clearspace:dateToText>2 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Intel E5530 vs Intel L5530</title>
      <link>http://communities.vmware.com/message/1366724</link>
      <description>&lt;br /&gt;
It appears from that chart that their are a number of differences, more than just turbo boost.&lt;br /&gt;
&lt;br /&gt;
&lt;table class="jive-wiki-table"&gt;
&lt;tr&gt;
&lt;td&gt;Intel&amp;reg; Virtualization Technology&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Execute Disable Bit&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Enhanced Intel&amp;reg; Speedstep Technology&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Enhanced Halt State (C1E)&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Intel&amp;reg; 64&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Intel&amp;reg; Demand Based Switching&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Intel&amp;reg; Turbo Boost Technology&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/false.gif" alt="http://null/inc/images/false.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Intel&amp;reg; Hyper-Threading Technology&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Intel&amp;reg; Trusted Execution Technology&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/false.gif" alt="http://null/inc/images/false.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Intel&amp;reg; Virtualization Technology for Directed I/O&lt;/td&gt;
&lt;td&gt;&amp;nbsp;&lt;/td&gt;
&lt;td&gt;&lt;img src="http://null/inc/images/true.gif" alt="http://null/inc/images/true.gif" class="jive-image"  /&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;br clear="left" /&gt;
&lt;p /&gt;</description>
      <pubDate>Thu, 17 Sep 2009 17:29:34 GMT</pubDate>
      <author>LucasAlbers</author>
      <guid>http://communities.vmware.com/message/1366724</guid>
      <dc:date>2009-09-17T17:29:34Z</dc:date>
      <clearspace:dateToText>2 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
  </channel>
</rss>

