<?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: Run process in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/run-process/m-p/3314402#M186237</link>
    <description>imagine in the simplest case, a server running one process, which does the following: -&lt;BR /&gt;&lt;BR /&gt;does a quick calculation&lt;BR /&gt;writes a lot of data to the disk&lt;BR /&gt;does another calculatation&lt;BR /&gt;writes a lot of data to the disk&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;As the program is running sequentially, it cannot get to the next "does another calculation" until it has finished "writing a lot of data to the disk".&lt;BR /&gt;&lt;BR /&gt;So as you can see, when it's waiting for the OS to write to disk, it simply cannot do the calculations, and therefore use the CPU.&lt;BR /&gt;&lt;BR /&gt;As this is a database re-index, the majority of work will be disk activity, and therefore it is that which is limiting the CPU usage.  &lt;BR /&gt;&lt;BR /&gt;The process cannot actually do anything with the spare CPU.&lt;BR /&gt;&lt;BR /&gt;If you're worried about not using all your CPU, write a separate program that calculates prime numbers or something ;)</description>
    <pubDate>Thu, 24 Jun 2004 08:59:44 GMT</pubDate>
    <dc:creator>Simon Hargrave</dc:creator>
    <dc:date>2004-06-24T08:59:44Z</dc:date>
    <item>
      <title>Run process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/run-process/m-p/3314399#M186234</link>
      <description>I run the database re-index job in the system , it require lots of memory and CPU to process it , but I found that this job only use about 40% CPU  ,and the other 60% is nearly free , how can I make the job can use the max. of CPU and memory (eg . 95% ) ? thx.</description>
      <pubDate>Thu, 24 Jun 2004 08:26:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/run-process/m-p/3314399#M186234</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-06-24T08:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: Run process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/run-process/m-p/3314400#M186235</link>
      <description>you'll probably find that your process is limited by disk I/O, and that the reason it's not using more CPU is because it's waiting for disk read/writes.&lt;BR /&gt;&lt;BR /&gt;sar -d should show how busy your disks are, and if they are maxing out.</description>
      <pubDate>Thu, 24 Jun 2004 08:29:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/run-process/m-p/3314400#M186235</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2004-06-24T08:29:59Z</dc:date>
    </item>
    <item>
      <title>Re: Run process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/run-process/m-p/3314401#M186236</link>
      <description>thx reply , what is mean waiting I/O ? is it using the max. of system resource ? it not , can I make use this idle resource ? thx.</description>
      <pubDate>Thu, 24 Jun 2004 08:54:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/run-process/m-p/3314401#M186236</guid>
      <dc:creator>peterchu</dc:creator>
      <dc:date>2004-06-24T08:54:22Z</dc:date>
    </item>
    <item>
      <title>Re: Run process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/run-process/m-p/3314402#M186237</link>
      <description>imagine in the simplest case, a server running one process, which does the following: -&lt;BR /&gt;&lt;BR /&gt;does a quick calculation&lt;BR /&gt;writes a lot of data to the disk&lt;BR /&gt;does another calculatation&lt;BR /&gt;writes a lot of data to the disk&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;As the program is running sequentially, it cannot get to the next "does another calculation" until it has finished "writing a lot of data to the disk".&lt;BR /&gt;&lt;BR /&gt;So as you can see, when it's waiting for the OS to write to disk, it simply cannot do the calculations, and therefore use the CPU.&lt;BR /&gt;&lt;BR /&gt;As this is a database re-index, the majority of work will be disk activity, and therefore it is that which is limiting the CPU usage.  &lt;BR /&gt;&lt;BR /&gt;The process cannot actually do anything with the spare CPU.&lt;BR /&gt;&lt;BR /&gt;If you're worried about not using all your CPU, write a separate program that calculates prime numbers or something ;)</description>
      <pubDate>Thu, 24 Jun 2004 08:59:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/run-process/m-p/3314402#M186237</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2004-06-24T08:59:44Z</dc:date>
    </item>
  </channel>
</rss>

