<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Virtualization Frontier</title>
    <link>http://communities.vmware.com/blogs/ToddMuirhead</link>
    <description>Some Stuff on Enterprise Virtualization from DellTechCenter</description>
    <pubDate>Fri, 05 Sep 2008 18:12:58 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-09-05T18:12:58Z</dc:date>
    <item>
      <title>Measuring Total CPU Utilization on Hyper-V</title>
      <link>http://communities.vmware.com/blogs/ToddMuirhead/2008/09/05/measuring-total-cpu-utilization-on-hyperv</link>
      <description>&lt;br /&gt;
I just finished up testing for a new whitepaper on Hyper-V performance and one of the initial things I had to figure out was how to measure the CPU utilization on the server. What is known as the parent partition (the initial Windows Server 2008 that is installed on the server and then used to enable the Hyper-V role) does not include the CPU utilization for its VMs in the main Processor Utilization performance counter. This was surprising to me at first, but makes sense when you consider the &lt;a class="jive-link-external" href="http://msdn.microsoft.com/en-us/library/cc768520.aspx"&gt;architecture of Hyper-V&lt;/a&gt;. In this architecture, the VMs do not go through the parent partition to access the processors. (Although I/O does to use the device drivers of the parent partition.)&lt;br /&gt;
&lt;br /&gt;
In order to solve this problem Microsoft has created some new performance counters that are specific to the Hyper-V Hypervisor. Early on in the betas for Hyper-V it wasn't clear what these counters did, as I &lt;a class="jive-link-external" href="http://www.delltechcenter.com/page/1%2F15%2F08+-+Perfmon+with+Hyper-V"&gt;blogged about back in January&lt;/a&gt;, but it is now much clearer with some &lt;a class="jive-link-external" href="http://blogs.technet.com/tonyso/archive/2008/08/12/performance-tuning-for-hyper-v-servers.aspx#3106546"&gt;guides from Microsoft&lt;/a&gt;. &lt;br /&gt;
&lt;br /&gt;
In order to measure the total CPU utilization on a Windows Server 2008 system running VMs under Hyper-V use the Hyper-V Hypervisor Logical Processor % Total Run Time counter in Performance Monitor (more affectionately known as perfmon). If you just look at the % CPU Utilization or the performance tab of Task Manager you will only see the CPU utilization of the parent partition and not the VMs.&lt;br /&gt;
&lt;p /&gt;
Todd</description>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">delltechcenter</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">hyper-v</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">performance</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">perfmon</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">cpu</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">utilization</category>
      <pubDate>Fri, 05 Sep 2008 18:11:00 GMT</pubDate>
      <author>ToddMuirhead</author>
      <guid>http://communities.vmware.com/blogs/ToddMuirhead/2008/09/05/measuring-total-cpu-utilization-on-hyperv</guid>
      <dc:date>2008-09-05T18:11:00Z</dc:date>
      <clearspace:dateToText>2 months, 2 weeks ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/ToddMuirhead/comment/measuring-total-cpu-utilization-on-hyperv</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/ToddMuirhead/feeds/comments?blogPostID=2141</wfw:commentRss>
    </item>
    <item>
      <title>Array Level MD3000i Performance Monitoring</title>
      <link>http://communities.vmware.com/blogs/ToddMuirhead/2008/07/15/array-level-md3000i-performance-monitoring</link>
      <description>During the weekly &lt;a class="jive-link-external" href="http://www.delltechcenter.com/page/Chat+Topics+and+Transcr+ipts"&gt;DellTechCenter Tech Tuesday&lt;/a&gt; chat a &lt;a class="jive-link-external" href="http://www.delltechcenter.com/page/07-01-2008+Benefits+of+iSCSI+with+Virtualization"&gt;couple of weeks ago&lt;/a&gt; a question came up about performance monitoring with the PowerVault MD3000i iSCSI array. The initial question was how to do performance monitoring from Linux and we addressed it in a &lt;a class="jive-link-external" href="http://www.delltechcenter.com/thread/1625343/Performance+Monitoring+of+MD3000i+from+Linux"&gt;followup discussion thread&lt;/a&gt;. The answer at this point was to use iostat for Linux or perfmon in windows to monitor performance on each host that was attached to the MD3000i array. This lead to a follow on question which was how to monitor the performance for the entire array. &lt;br /&gt;
&lt;br /&gt;
The management tool for the MD3000i, PowerVault Modular Disk Storage Manager, does not include any performance stats beyond basic iSCSI port level stats. Some investigation into the &lt;a class="jive-link-external" href="http://support.dell.com/support/edocs/systems/md3000/en/CLI/PDF/CLIA00MR.pdf"&gt;command line interface for the MD3000i&lt;/a&gt; revealed that there is a command to capture the performance stats on the array. Using the smcli, which is installed as part of the MDSM, it is possible to collect the performance stats for the array, controllers, and virtual disks to a csv file. &lt;br /&gt;
&lt;br /&gt;
This turns out to be pretty cool and not too hard to do. Just a simple command and a little bit of spreadsheet magic and you too can produce cool performance graphs of your MD3000i. &lt;a class="jive-link-external" href="http://www.delltechcenter.com/page/MD3000i+Performance+Monitoring"&gt;The details are posted here on delltechcenter.com&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
Todd</description>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">delltechcenter</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">md3000i</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">iscsi</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">performance</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">perfmon</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">systat</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">smcli</category>
      <category domain="http://communities.vmware.com/blogs/ToddMuirhead/tags">powervault</category>
      <pubDate>Tue, 15 Jul 2008 18:37:00 GMT</pubDate>
      <author>ToddMuirhead</author>
      <guid>http://communities.vmware.com/blogs/ToddMuirhead/2008/07/15/array-level-md3000i-performance-monitoring</guid>
      <dc:date>2008-07-15T18:37:00Z</dc:date>
      <clearspace:dateToText>4 months, 1 week ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/ToddMuirhead/comment/array-level-md3000i-performance-monitoring</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/ToddMuirhead/feeds/comments?blogPostID=1944</wfw:commentRss>
    </item>
  </channel>
</rss>

