<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: MWA vs vmstat in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000262#M749776</link>
    <description>Well...from vmstat man page, it says the b column can be    "Blocked for resources (I/O, paging, etc.)"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Whereas the GBL_DISK_SUBSYSTEM_QUEUE is only for the disk I/O subsystem.&lt;BR /&gt;&lt;BR /&gt;As an example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high.  In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk &lt;BR /&gt;I/O subsystem.&lt;BR /&gt;&lt;BR /&gt;I got that from:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://ovweb.external.hp.com/ovnsmdps/pdf/ovpa450_hpux_dict_perf_metrics.txt" target="_blank"&gt;http://ovweb.external.hp.com/ovnsmdps/pdf/ovpa450_hpux_dict_perf_metrics.txt&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Maybe some of that will help.&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 15 May 2007 08:20:48 GMT</pubDate>
    <dc:creator>Geoff Wild</dc:creator>
    <dc:date>2007-05-15T08:20:48Z</dc:date>
    <item>
      <title>MWA vs vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000261#M749775</link>
      <description>Hi there,&lt;BR /&gt;&lt;BR /&gt;Question on vmstat, and Measureware performance&lt;BR /&gt;metrics on HP-UX 11.11 Superdome.&lt;BR /&gt;&lt;BR /&gt;I am seeing a very large discrepancy between vmstat blocked jobs and MWA.&lt;BR /&gt;&lt;BR /&gt;Using both tools to look at performance metrics vmstat on a 5 minute sample shows 'b' column values &amp;gt; 10 over a period of 4 hours.&lt;BR /&gt;&lt;BR /&gt;The equivalent column in MWA GBL_DISK_SUBSYSTEM_QUEUE (I believe) shows values of 0 over the same 4 hour period.&lt;BR /&gt;&lt;BR /&gt;I realise that underneath the hood they are both very different (KI vs pstat), and general conclusion is KI is more accurate ... but I would'nt have expected to see such a huge discrepancy.&lt;BR /&gt;&lt;BR /&gt;Can anyone explain why there would be such a difference ? i.e What have I missed/mis understood ?&lt;BR /&gt;&lt;BR /&gt;Thanks for all/any help&lt;BR /&gt;&lt;BR /&gt;John</description>
      <pubDate>Tue, 15 May 2007 08:08:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000261#M749775</guid>
      <dc:creator>John Mannion</dc:creator>
      <dc:date>2007-05-15T08:08:51Z</dc:date>
    </item>
    <item>
      <title>Re: MWA vs vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000262#M749776</link>
      <description>Well...from vmstat man page, it says the b column can be    "Blocked for resources (I/O, paging, etc.)"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Whereas the GBL_DISK_SUBSYSTEM_QUEUE is only for the disk I/O subsystem.&lt;BR /&gt;&lt;BR /&gt;As an example, the GBL_DISK_SUBSYSTEM_QUEUE values can be low, while the APP_DISK_SUBSYSTEM_WAIT_PCT values can be high.  In this case, there are many processes on the system, but there are only a very small number of processes in the specific application that is being examined and there is a high percentage of those few processes that are blocked on the disk &lt;BR /&gt;I/O subsystem.&lt;BR /&gt;&lt;BR /&gt;I got that from:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://ovweb.external.hp.com/ovnsmdps/pdf/ovpa450_hpux_dict_perf_metrics.txt" target="_blank"&gt;http://ovweb.external.hp.com/ovnsmdps/pdf/ovpa450_hpux_dict_perf_metrics.txt&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Maybe some of that will help.&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 15 May 2007 08:20:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000262#M749776</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2007-05-15T08:20:48Z</dc:date>
    </item>
    <item>
      <title>Re: MWA vs vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000263#M749777</link>
      <description>Thanks Geoff...&lt;BR /&gt;&lt;BR /&gt;Still am unsure though whats causing this&lt;BR /&gt;discrepancy though.&lt;BR /&gt;&lt;BR /&gt;Does anyone know what the equivalent&lt;BR /&gt;parameter(s) in Measureware are for the&lt;BR /&gt;vmstat "b" column ?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;John</description>
      <pubDate>Fri, 18 May 2007 07:00:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000263#M749777</guid>
      <dc:creator>John Mannion</dc:creator>
      <dc:date>2007-05-18T07:00:05Z</dc:date>
    </item>
    <item>
      <title>Re: MWA vs vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000264#M749778</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Meaurement discrepencies come from how the tools were written and how often the data is collected.&lt;BR /&gt;&lt;BR /&gt;Its also possible there is a bug. Is the system patched up to date?&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 18 May 2007 07:01:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000264#M749778</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-05-18T07:01:44Z</dc:date>
    </item>
    <item>
      <title>Re: MWA vs vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000265#M749779</link>
      <description>Hello John, &lt;BR /&gt;            As Geoff suggests they are measuring different things, there is no direct mwa equivalent that I know of .&lt;BR /&gt;MWA splits things down in to different measures so that you tell indvidual components apart and identify which ones need attention .&lt;BR /&gt;the b column in vmstat simply lists all the processes that can't be put on the run queue for an i/o related reason including disk i/o tape i/o paging  and I think things like NFS lan and terminal  &lt;BR /&gt;have a look a the B page in glance to get an idea of the things your system is waiting for.    &lt;BR /&gt;&lt;BR /&gt;Mike</description>
      <pubDate>Fri, 18 May 2007 08:05:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000265#M749779</guid>
      <dc:creator>BUPA IS</dc:creator>
      <dc:date>2007-05-18T08:05:33Z</dc:date>
    </item>
    <item>
      <title>Re: MWA vs vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000266#M749780</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Thanks everyone. I realise both tools are very different underneath the hood. I guess I was just trying to understand why on the face of it the "b" column in vmstat indicated a possible issue but we're not seeing any indication of an issue in MWA data. &lt;BR /&gt;&lt;BR /&gt;I will explore Patch level to make sure nothing was missed here.&lt;BR /&gt;&lt;BR /&gt;Once again, thats for all your help&lt;BR /&gt;&lt;BR /&gt;I'll post anything I find out ..&lt;BR /&gt;&lt;BR /&gt;John</description>
      <pubDate>Fri, 18 May 2007 09:25:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mwa-vs-vmstat/m-p/4000266#M749780</guid>
      <dc:creator>John Mannion</dc:creator>
      <dc:date>2007-05-18T09:25:42Z</dc:date>
    </item>
  </channel>
</rss>

