<?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: High load Average in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558545#M226065</link>
    <description>Thanks Olivier, that makes sense as I have java on both those systems.  I have a call open with HP and have to run some perfomance monitors, but it will just tell them the same as I see and have explained in the initial post.  &lt;BR /&gt;&lt;BR /&gt;Sally</description>
    <pubDate>Mon, 06 Jun 2005 12:06:22 GMT</pubDate>
    <dc:creator>Coolmar</dc:creator>
    <dc:date>2005-06-06T12:06:22Z</dc:date>
    <item>
      <title>High load Average</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558542#M226062</link>
      <description>Hi folks,&lt;BR /&gt;&lt;BR /&gt;I have a couple of hpux 11.11 systems that are showing a very high load average (uptime).  They are both in the 14-16 range, one of them got as high as 30.  The thing is that there are no processes at 90-100% and SAR is showing the system to be pretty-much idle.  The thing is that the system is running fine.  In the past, whenever a system has a load average above 5, we would notice right away because the system would be so slow.  Any ideas?</description>
      <pubDate>Mon, 06 Jun 2005 09:57:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558542#M226062</guid>
      <dc:creator>Coolmar</dc:creator>
      <dc:date>2005-06-06T09:57:05Z</dc:date>
    </item>
    <item>
      <title>Re: High load Average</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558543#M226063</link>
      <description>Hi Sally,&lt;BR /&gt;&lt;BR /&gt;Can you post those 2 files:&lt;BR /&gt;&lt;BR /&gt;#vmstat -dnS 6 100 &amp;gt; vmstat.log&lt;BR /&gt;#sar -bv 6 100 &amp;gt; sar.log&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;&lt;BR /&gt;Eric Antunes</description>
      <pubDate>Mon, 06 Jun 2005 10:23:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558543#M226063</guid>
      <dc:creator>Eric Antunes</dc:creator>
      <dc:date>2005-06-06T10:23:49Z</dc:date>
    </item>
    <item>
      <title>Re: High load Average</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558544#M226064</link>
      <description>I've been seeing the same behaviour on my systems for the last two years or so. I even opened a call at HP about this but I didn't get any definite and satisfactory explanation.&lt;BR /&gt;&lt;BR /&gt;In my opinion, the load average is no longer a good performance measure, at least when taken from the traditional tools (top, uptime, etc). Glance is more realistic when giving out performance metrics.&lt;BR /&gt;&lt;BR /&gt;In the older years, having a load over 10 meant we were in trouble. It's no longer the case. I ran some tests with a special CPU hogging program taken from the HP Performance and Monitoring course (waste.c) and by tweaking it, I've been able to artificially inflate the load average to over 100 - and the system was still responding correctly. &lt;BR /&gt;&lt;BR /&gt;The waste.c description in the source is that it "slips all of its processing in between clock ticks".&lt;BR /&gt;&lt;BR /&gt;It seems that most modern processes, especially java-based, have lots of threads. I *THINK* that these threads might get executed within a very short period like the waste.c program does, and this might explain why we get high load averages.&lt;BR /&gt;&lt;BR /&gt;In my case, I changed our  monitoring scripts to report problems if the load average goes beyond 30. It's much higher than before, but it works well.&lt;BR /&gt;&lt;BR /&gt;Good luck&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 06 Jun 2005 11:39:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558544#M226064</guid>
      <dc:creator>Olivier Masse</dc:creator>
      <dc:date>2005-06-06T11:39:45Z</dc:date>
    </item>
    <item>
      <title>Re: High load Average</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558545#M226065</link>
      <description>Thanks Olivier, that makes sense as I have java on both those systems.  I have a call open with HP and have to run some perfomance monitors, but it will just tell them the same as I see and have explained in the initial post.  &lt;BR /&gt;&lt;BR /&gt;Sally</description>
      <pubDate>Mon, 06 Jun 2005 12:06:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558545#M226065</guid>
      <dc:creator>Coolmar</dc:creator>
      <dc:date>2005-06-06T12:06:22Z</dc:date>
    </item>
    <item>
      <title>Re: High load Average</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558546#M226066</link>
      <description>also, keep an eye on the memory metric.. java tends to be resident memory based.  might run glance and ps -elx to spot heavy memory consumers.  if your free-memory becomes an issue, then consult the jvm experts to tune the starting parameters of java, such as heap-size, etc.. also, hit the &lt;A href="http://www.hp.com/go/java" target="_blank"&gt;http://www.hp.com/go/java&lt;/A&gt; site for know patches for performance.</description>
      <pubDate>Mon, 06 Jun 2005 21:43:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/high-load-average/m-p/3558546#M226066</guid>
      <dc:creator>D Block 2</dc:creator>
      <dc:date>2005-06-06T21:43:00Z</dc:date>
    </item>
  </channel>
</rss>

