<?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: vmstat in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261680#M472181</link>
    <description>The section fault is not showing about your page faults ( memory ).  But it shows about your VM system level faults.&lt;BR /&gt;&lt;BR /&gt;in -&amp;gt; Device interrupts&lt;BR /&gt;sy -&amp;gt; System calls&lt;BR /&gt;cs -&amp;gt; CPU content switch rate.&lt;BR /&gt;&lt;BR /&gt;Here, you have high number of system calls, and very low device interrupts and CPU switching.&lt;BR /&gt;&lt;BR /&gt;You cannot simply depends on vmstat output.  You may have to look for some other utilities to find out, what raised so much system calls.  Whether it is from user generated or something else.  You can use sar or glance to find out that.&lt;BR /&gt;&lt;BR /&gt;Second it depends on your system load.  I think, it is reasonable value.  I have seen many production environment, sy is always higher.</description>
    <pubDate>Fri, 05 Nov 2010 07:08:44 GMT</pubDate>
    <dc:creator>Shibin_2</dc:creator>
    <dc:date>2010-11-05T07:08:44Z</dc:date>
    <item>
      <title>vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261676#M472177</link>
      <description>kthr memory page disk faults cpu&lt;BR /&gt;r b w swap free re mf pi po fr de sr m0 m1 m5 m6 in sy cs us sy id&lt;BR /&gt;0 0 0 22182880 6451048 61 183 11 12 12 0 0 0 22 2 1 971 2316 743 1 1 99&lt;BR /&gt;&lt;BR /&gt;Does the high number of faults in the vmstat really matter</description>
      <pubDate>Fri, 05 Nov 2010 01:49:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261676#M472177</guid>
      <dc:creator>David Willams</dc:creator>
      <dc:date>2010-11-05T01:49:00Z</dc:date>
    </item>
    <item>
      <title>Re: vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261677#M472178</link>
      <description>Yes. You need to find out, what processes are trying to utilize.</description>
      <pubDate>Fri, 05 Nov 2010 02:26:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261677#M472178</guid>
      <dc:creator>Shibin_2</dc:creator>
      <dc:date>2010-11-05T02:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261678#M472179</link>
      <description>but the system idle time is very high and mem. utilization is very very low...&lt;BR /&gt;&lt;BR /&gt;faults&lt;BR /&gt;-------&lt;BR /&gt;in     sys     cs&lt;BR /&gt;1340   28765   4657&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;What does the above mean and how critical it could be.&lt;BR /&gt;&lt;BR /&gt;What are the other factors that need checking.</description>
      <pubDate>Fri, 05 Nov 2010 02:37:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261678#M472179</guid>
      <dc:creator>David Willams</dc:creator>
      <dc:date>2010-11-05T02:37:08Z</dc:date>
    </item>
    <item>
      <title>Re: vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261679#M472180</link>
      <description>Hi,&lt;BR /&gt;if you have glance, you can narrow down problem easily. &lt;BR /&gt;&lt;BR /&gt;OR you can go ;&lt;BR /&gt;&lt;A href="http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1288943634877+28353475&amp;amp;threadId=119443" target="_blank"&gt;http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1288943634877+28353475&amp;amp;threadId=119443&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;and pick up html docs from JRF's post they are very useful.</description>
      <pubDate>Fri, 05 Nov 2010 07:00:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261679#M472180</guid>
      <dc:creator>Hakki Aydin Ucar</dc:creator>
      <dc:date>2010-11-05T07:00:07Z</dc:date>
    </item>
    <item>
      <title>Re: vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261680#M472181</link>
      <description>The section fault is not showing about your page faults ( memory ).  But it shows about your VM system level faults.&lt;BR /&gt;&lt;BR /&gt;in -&amp;gt; Device interrupts&lt;BR /&gt;sy -&amp;gt; System calls&lt;BR /&gt;cs -&amp;gt; CPU content switch rate.&lt;BR /&gt;&lt;BR /&gt;Here, you have high number of system calls, and very low device interrupts and CPU switching.&lt;BR /&gt;&lt;BR /&gt;You cannot simply depends on vmstat output.  You may have to look for some other utilities to find out, what raised so much system calls.  Whether it is from user generated or something else.  You can use sar or glance to find out that.&lt;BR /&gt;&lt;BR /&gt;Second it depends on your system load.  I think, it is reasonable value.  I have seen many production environment, sy is always higher.</description>
      <pubDate>Fri, 05 Nov 2010 07:08:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261680#M472181</guid>
      <dc:creator>Shibin_2</dc:creator>
      <dc:date>2010-11-05T07:08:44Z</dc:date>
    </item>
    <item>
      <title>Re: vmstat</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261681#M472182</link>
      <description>thanks</description>
      <pubDate>Wed, 10 Nov 2010 07:49:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmstat/m-p/5261681#M472182</guid>
      <dc:creator>David Willams</dc:creator>
      <dc:date>2010-11-10T07:49:39Z</dc:date>
    </item>
  </channel>
</rss>

