<?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: Lot of pagefaults in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681380#M53113</link>
    <description>hi,&lt;BR /&gt;&lt;BR /&gt;  The value to look for is pageout (po) through the vmstat -n command. If it is showing numbers corresponding to po constantly then there is a memory pressure. It should be ideally 0.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;raj</description>
    <pubDate>Tue, 12 Mar 2002 19:57:53 GMT</pubDate>
    <dc:creator>Roger Baptiste</dc:creator>
    <dc:date>2002-03-12T19:57:53Z</dc:date>
    <item>
      <title>Lot of pagefaults</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681374#M53107</link>
      <description>Server - HP K460 2CPU 1.75GB &lt;BR /&gt;O/S    - HP-UX 10.20&lt;BR /&gt;&lt;BR /&gt;Whenever I am looking through the memory reports by Glance I found that there are lot of pagefaults. I have checked through mstm, it has not logged any error for the memory. Can anybody please let me know what are the possible area I can look for the page faults. Here is a output of glance memory report.&lt;BR /&gt;&lt;BR /&gt;Page Faults         5      3402253         0.9      281.1      3663.0&lt;BR /&gt;Paging Requests     0      1252338         0.0      103.5      1403.0&lt;BR /&gt;KB Paged In       0kb       10.8mb         0.0        0.9    806596.1&lt;BR /&gt;KB Paged Out      0kb          4kb         0.0        0.0         0.7&lt;BR /&gt;Reactivations       0            0         0.0        0.0         0.0&lt;BR /&gt;Deactivations       0            0         0.0        0.0         0.0&lt;BR /&gt;KB Reactivated    0kb          0kb         0.0        0.0         0.0&lt;BR /&gt;KB Deactivated    0kb          4kb         0.0        0.0         0.7&lt;BR /&gt;VM Reads            0          642         0.0        0.0        24.0&lt;BR /&gt;VM Writes           0            0         0.0        0.0         0.0&lt;BR /&gt;&lt;BR /&gt;Total VM : 835.7mb   Sys Mem  : 161.9mb   User Mem:  1.25gb   Phys Mem:  1.75gb&lt;BR /&gt;Active VM: 171.9mb   Buf Cache: 268.8mb   Free Mem:  77.9mb</description>
      <pubDate>Tue, 12 Mar 2002 16:40:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681374#M53107</guid>
      <dc:creator>Sandip Ghosh</dc:creator>
      <dc:date>2002-03-12T16:40:48Z</dc:date>
    </item>
    <item>
      <title>Re: Lot of pagefaults</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681375#M53108</link>
      <description>Hi Sandip,&lt;BR /&gt;&lt;BR /&gt;seems like your swapspace is not enough. Try to add some swapspace, as much, that you get at least as total RAM amount. Hope this will do it for you.&lt;BR /&gt;&lt;BR /&gt;Allways stay on the bright side of life!&lt;BR /&gt;&lt;BR /&gt;Peter</description>
      <pubDate>Tue, 12 Mar 2002 16:45:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681375#M53108</guid>
      <dc:creator>Peter Kloetgen</dc:creator>
      <dc:date>2002-03-12T16:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: Lot of pagefaults</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681376#M53109</link>
      <description>Page Faults are an inevitable part of managing memory. &lt;BR /&gt;&lt;BR /&gt;They are not really a "fault", just an indication that the page reference could not be found in in the TLB Cache, so had to be looked for elsewhere. This is part opf the PA-RISC architecture.&lt;BR /&gt;&lt;BR /&gt;I have tried to look for a resolution to this one myself, but have yet to find an answer other than "upgrade to a bigger CPU with a bigger cache".&lt;BR /&gt;&lt;BR /&gt;(Most of this info was pilfered from the Memory Management White Paper)&lt;BR /&gt;&lt;BR /&gt;Cheers, Ian</description>
      <pubDate>Tue, 12 Mar 2002 16:48:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681376#M53109</guid>
      <dc:creator>Ian Dennison_1</dc:creator>
      <dc:date>2002-03-12T16:48:26Z</dc:date>
    </item>
    <item>
      <title>Re: Lot of pagefaults</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681377#M53110</link>
      <description>&lt;BR /&gt;page fault&lt;BR /&gt;&lt;BR /&gt;An event recorded when a process tries to execute code instructions or to reference a data page not resident in a process' mapped physical memory.  The system must page-in the missing code or data to allow execution to continue.&lt;BR /&gt;&lt;BR /&gt;Just a "feature" of virtual memory. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/5965-4641/5965-4641_top.html" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/5965-4641/5965-4641_top.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Mar 2002 16:49:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681377#M53110</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2002-03-12T16:49:59Z</dc:date>
    </item>
    <item>
      <title>Re: Lot of pagefaults</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681378#M53111</link>
      <description>Hi Peter,&lt;BR /&gt;&lt;BR /&gt;There is no swapping at all in the swapdevices. It is swapping 0% on the swap devices.&lt;BR /&gt;&lt;BR /&gt;/dev/vg00/lvol2                device         512          0        1&lt;BR /&gt;/dev/vg01/lvol9                device        1024          0        0&lt;BR /&gt;pseudo-swap                    memory        1329        396       na&lt;BR /&gt;&lt;BR /&gt;Sandip</description>
      <pubDate>Tue, 12 Mar 2002 16:50:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681378#M53111</guid>
      <dc:creator>Sandip Ghosh</dc:creator>
      <dc:date>2002-03-12T16:50:35Z</dc:date>
    </item>
    <item>
      <title>Re: Lot of pagefaults</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681379#M53112</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;Page faults are perfectly normal and do not usually indicate a problem. It simply means that an address could not be resolved in the Translation Lookaside Buffer (TLB) and that the system then had to go out to the much slower memory. Remember the TLB is quite small and thus page faults are inevitable. Something that you should worry about is a high pageout rate; that indicates swapping (well, paging actually) and your performance will degrade.&lt;BR /&gt;&lt;BR /&gt;Regards, Clay&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Mar 2002 16:52:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681379#M53112</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2002-03-12T16:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: Lot of pagefaults</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681380#M53113</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;  The value to look for is pageout (po) through the vmstat -n command. If it is showing numbers corresponding to po constantly then there is a memory pressure. It should be ideally 0.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;raj</description>
      <pubDate>Tue, 12 Mar 2002 19:57:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lot-of-pagefaults/m-p/2681380#M53113</guid>
      <dc:creator>Roger Baptiste</dc:creator>
      <dc:date>2002-03-12T19:57:53Z</dc:date>
    </item>
  </channel>
</rss>

