<?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: Disk IO and run queue length in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-io-and-run-queue-length/m-p/4665872#M381422</link>
    <description>Any idea about AIX? It on a 4 CPU machine, it shows me load average of 7 but CPU usage is around 80%</description>
    <pubDate>Mon, 26 Jul 2010 04:34:08 GMT</pubDate>
    <dc:creator>Salman Ahmed Qureshi</dc:creator>
    <dc:date>2010-07-26T04:34:08Z</dc:date>
    <item>
      <title>Disk IO and run queue length</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-io-and-run-queue-length/m-p/4665870#M381420</link>
      <description>Hi,&lt;BR /&gt;If a process is waiting for disk IO con complete, is it added to the run queue length? For example, if on a 2 CPU machine, if there are two processes are waiting for CPU and 2 are waiting for IO to complete before asking from the CPU tipe, would run queue length be 4 in this case? or Run queue lenght is calculate only on the bases of the processes waiting for the CPU?&lt;BR /&gt;Thanks</description>
      <pubDate>Mon, 26 Jul 2010 01:38:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-io-and-run-queue-length/m-p/4665870#M381420</guid>
      <dc:creator>Salman Ahmed Qureshi</dc:creator>
      <dc:date>2010-07-26T01:38:41Z</dc:date>
    </item>
    <item>
      <title>Re: Disk IO and run queue length</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-io-and-run-queue-length/m-p/4665871#M381421</link>
      <description>V. Salom , &lt;BR /&gt;On HP-UX 11i, this does not include processes/threads that are waiting for IO to complete, i.e., high-priority sleepers. On previous versions of HP-UX, the Load Average included hi-priority sleepers , and as such the Average load shown might not be accurate.&lt;BR /&gt;Regards, &lt;BR /&gt;TheFrogIsDeaf.</description>
      <pubDate>Mon, 26 Jul 2010 03:18:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-io-and-run-queue-length/m-p/4665871#M381421</guid>
      <dc:creator>DeafFrog</dc:creator>
      <dc:date>2010-07-26T03:18:55Z</dc:date>
    </item>
    <item>
      <title>Re: Disk IO and run queue length</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-io-and-run-queue-length/m-p/4665872#M381422</link>
      <description>Any idea about AIX? It on a 4 CPU machine, it shows me load average of 7 but CPU usage is around 80%</description>
      <pubDate>Mon, 26 Jul 2010 04:34:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-io-and-run-queue-length/m-p/4665872#M381422</guid>
      <dc:creator>Salman Ahmed Qureshi</dc:creator>
      <dc:date>2010-07-26T04:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: Disk IO and run queue length</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-io-and-run-queue-length/m-p/4665873#M381423</link>
      <description>&lt;!--!*#--&gt;Hi,&lt;BR /&gt;  The processes waiting for IO  will not accounted for CPU RUN QUEUE calculation. The process is mainly blocked for disk activity and not for CPU.&lt;BR /&gt;&lt;BR /&gt;  In AIX, how many physical processors are there in the system? If it is 4, then you might have enable multithreading in which case the total processors are 8. Load average of 7 is not accounting for 100% CPU utilization.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Muru</description>
      <pubDate>Tue, 27 Jul 2010 03:20:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-io-and-run-queue-length/m-p/4665873#M381423</guid>
      <dc:creator>muruganantham raju</dc:creator>
      <dc:date>2010-07-27T03:20:30Z</dc:date>
    </item>
  </channel>
</rss>

