<?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: Programmatically obtaining kernel metric info.. in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/programmatically-obtaining-kernel-metric-info/m-p/3425393#M707385</link>
    <description>A bit more investigation: top / ps / sar all use the pstat APIs.  Glance appears to use the kernel instrumentation APIs defined in ki.h (but documentation on these appears to be sketchy at best).</description>
    <pubDate>Thu, 25 Nov 2004 09:00:26 GMT</pubDate>
    <dc:creator>David Gourley</dc:creator>
    <dc:date>2004-11-25T09:00:26Z</dc:date>
    <item>
      <title>Programmatically obtaining kernel metric info..</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/programmatically-obtaining-kernel-metric-info/m-p/3425390#M707382</link>
      <description>Does anyone know any mechanism to obtain some of the more interesting Glance style metrics programmatically?  &lt;BR /&gt;&lt;BR /&gt;For example, I know that data equivalent to many of the metrics can be obtained from the pstat* APIs.  However there are a number of really interesting metrics which I can't see corresponding pstat APIs to, e.g. GBL_PRI_QUEUE, GBL_CPU_CSWITCH_UTIL (and a number of others related to queue size on particular kernel resources).  From reading HP-UX 11i Tuning and Performance, it appears that there are a number of non-idle activities which may show up as idle time with the simpler APIs - is there any way to find out how much *useful* CPU time is used without loading Glance?&lt;BR /&gt;&lt;BR /&gt;There are issues with Glance's footprint for the particular problem I'm investigating.</description>
      <pubDate>Thu, 18 Nov 2004 12:14:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/programmatically-obtaining-kernel-metric-info/m-p/3425390#M707382</guid>
      <dc:creator>David Gourley</dc:creator>
      <dc:date>2004-11-18T12:14:19Z</dc:date>
    </item>
    <item>
      <title>Re: Programmatically obtaining kernel metric info..</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/programmatically-obtaining-kernel-metric-info/m-p/3425391#M707383</link>
      <description>I am attaching some sar based data collection scripts. They may work for you.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 18 Nov 2004 12:15:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/programmatically-obtaining-kernel-metric-info/m-p/3425391#M707383</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-11-18T12:15:37Z</dc:date>
    </item>
    <item>
      <title>Re: Programmatically obtaining kernel metric info..</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/programmatically-obtaining-kernel-metric-info/m-p/3425392#M707384</link>
      <description>"is there any way to find out how much *useful* CPU time is used without loading Glance"&lt;BR /&gt;&lt;BR /&gt;Try top -f [filename] -d [count]&lt;BR /&gt;&lt;BR /&gt;where "filename" is where you want the output saved, and "count" is the number of iterations.&lt;BR /&gt;&lt;BR /&gt;mark</description>
      <pubDate>Thu, 18 Nov 2004 13:47:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/programmatically-obtaining-kernel-metric-info/m-p/3425392#M707384</guid>
      <dc:creator>Mark Greene_1</dc:creator>
      <dc:date>2004-11-18T13:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: Programmatically obtaining kernel metric info..</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/programmatically-obtaining-kernel-metric-info/m-p/3425393#M707385</link>
      <description>A bit more investigation: top / ps / sar all use the pstat APIs.  Glance appears to use the kernel instrumentation APIs defined in ki.h (but documentation on these appears to be sketchy at best).</description>
      <pubDate>Thu, 25 Nov 2004 09:00:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/programmatically-obtaining-kernel-metric-info/m-p/3425393#M707385</guid>
      <dc:creator>David Gourley</dc:creator>
      <dc:date>2004-11-25T09:00:26Z</dc:date>
    </item>
  </channel>
</rss>

