<?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: Async IO is NOT ?? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938857#M762855</link>
    <description>&lt;!--!*#--&gt;Hi,&lt;BR /&gt; &lt;BR /&gt;asynchronous I/O is, as far as I/O performance is concerned, by far the most advantageous technique.&lt;BR /&gt;However, on HP-UX it only seems to work with raw I/O, i.e. writing to raw devices, which at its downside may increase the administrative overhead.&lt;BR /&gt;From our Oracle DBA, who has access to the so called Oracle Metalink knowledge base, I was given a document that deals on this topic whose ID was "Metalink No. 139272.1".&lt;BR /&gt;I am uncertain about copyright issues why I refrain from attaching the doc to my reply.&lt;BR /&gt;Maybe you can find someone at your site who can browse the Oracle Metalinks?&lt;BR /&gt;The prevelance of async I/O may be detected by the existence of an async I/O device and Oracle DB writer processes which access it.&lt;BR /&gt;Since we are only using cooked I/O with our Oracle DB servers (our clients demand that) but all of our Informix DB servers are using it I can only demonstrate for an Informix box .&lt;BR /&gt;&lt;BR /&gt;e.g.&lt;BR /&gt;&lt;BR /&gt;# ll /dev/async*&lt;BR /&gt;crw-rw-rw-   1 bin        bin        101 0x000000 Dec  2  2005 /dev/async&lt;BR /&gt;crw-rw-rw-   1 bin        bin        101 0x000000 Dec  2  2005 /dev/asyncdsk&lt;BR /&gt; &lt;BR /&gt;# ps -fp "$(fuser -u /dev/async 2&amp;gt;/dev/null)"&lt;BR /&gt;ps: wrong PID number&lt;BR /&gt;     UID   PID  PPID  C    STIME TTY       TIME COMMAND&lt;BR /&gt;informix 29952 29951  0  Jan  8  ?         4:52 /opt/inf_99/bin/oninit -v&lt;BR /&gt;    root  1945     1  0  Dec 28  ?        200:55 /opt/inf_96/bin/oninit -v&lt;BR /&gt;    root  1947  1946  0  Dec 28  ?        72:37 /opt/inf_96/bin/oninit -v&lt;BR /&gt;informix  1812     1  0  Jan  8  ?        219:56 /opt/inf_altdb/bin/oninit -v&lt;BR /&gt;    root  1961     1  0  Dec 28  ?        44:49 /opt/inf_97/bin/oninit -v&lt;BR /&gt;    root  1964  1963  0  Dec 28  ?        53:46 /opt/inf_97/bin/oninit -v&lt;BR /&gt;informix 29950     1  0  Jan  8  ?        20:33 /opt/inf_99/bin/oninit -v&lt;BR /&gt;informix  1818  1813  0  Jan  8  ?        240:09 /opt/inf_altdb/bin/oninit -v&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;As you can see with Informix the crucial DB processes are called oninit.&lt;BR /&gt;&lt;BR /&gt;You can also check for the existence of the async driver in your running kernel.&lt;BR /&gt;  &lt;BR /&gt;# strings /stand/vmunix|grep async&lt;BR /&gt;fs_async&lt;BR /&gt;max_async_ports&lt;BR /&gt;Maximum Number of asyncdsk Ports That Can be Open At One Time&lt;BR /&gt;asyncdsk&lt;BR /&gt;asyncdsk_included&lt;BR /&gt;fs_async        1&lt;BR /&gt;asyncdsk_included&lt;BR /&gt;asyncdsk&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;# lsdev -d asyncdsk&lt;BR /&gt;    Character     Block       Driver          Class&lt;BR /&gt;      101          -1         asyncdsk        pseudo&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;And last but not least, a couple of async I/O related kernel tunable must be set, like these:&lt;BR /&gt; &lt;BR /&gt;# kmtune -q fs_async -q max_async_ports&lt;BR /&gt;Parameter             Current Dyn Planned                    Module     Version&lt;BR /&gt;===============================================================================&lt;BR /&gt;fs_async                    1  -  1&lt;BR /&gt;max_async_ports            50  -  50&lt;BR /&gt; &lt;BR /&gt;# kmtune|grep aio&lt;BR /&gt;aio_listio_max            256  -  256&lt;BR /&gt;aio_max_ops              2048  -  2048&lt;BR /&gt;aio_physmem_pct            10  -  10&lt;BR /&gt;aio_prio_delta_max         20  -  20</description>
    <pubDate>Tue, 06 Feb 2007 03:49:57 GMT</pubDate>
    <dc:creator>Ralph Grothe</dc:creator>
    <dc:date>2007-02-06T03:49:57Z</dc:date>
    <item>
      <title>Async IO is NOT ??</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938854#M762852</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;i am using oracle 10g RAC(to nodes) over HP-UX 11i R2(on rp3440/9000 server) using shared RAW storage(HP-EVA HSV100).&lt;BR /&gt;is it possiable to use Async IO ??&lt;BR /&gt;how can i find that either my machine using Async IO or not ??&lt;BR /&gt;if my machine is not using Async IO, how may activate it ??&lt;BR /&gt;&lt;BR /&gt;looking from your kind response.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;Deep</description>
      <pubDate>Mon, 05 Feb 2007 23:13:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938854#M762852</guid>
      <dc:creator>Deep C Pandey</dc:creator>
      <dc:date>2007-02-05T23:13:23Z</dc:date>
    </item>
    <item>
      <title>Re: Async IO is NOT ??</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938855#M762853</link>
      <description>hi Deep,&lt;BR /&gt;&lt;BR /&gt;First of all, see is async io is configured on your system.&lt;BR /&gt;&lt;BR /&gt;see the following thread on how to configure and verify:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1077712" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1077712&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;hope this helps!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;kind regards&lt;BR /&gt;yogeeraj</description>
      <pubDate>Tue, 06 Feb 2007 03:11:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938855#M762853</guid>
      <dc:creator>Yogeeraj_1</dc:creator>
      <dc:date>2007-02-06T03:11:12Z</dc:date>
    </item>
    <item>
      <title>Re: Async IO is NOT ??</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938856#M762854</link>
      <description>Shalom Deep,&lt;BR /&gt;&lt;BR /&gt;Yes async i/o is possible with your hardware setup.&lt;BR /&gt;&lt;BR /&gt;Some will argue as to whether its true async.&lt;BR /&gt;&lt;BR /&gt;By default in this OS is should be active.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 06 Feb 2007 03:38:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938856#M762854</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-02-06T03:38:23Z</dc:date>
    </item>
    <item>
      <title>Re: Async IO is NOT ??</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938857#M762855</link>
      <description>&lt;!--!*#--&gt;Hi,&lt;BR /&gt; &lt;BR /&gt;asynchronous I/O is, as far as I/O performance is concerned, by far the most advantageous technique.&lt;BR /&gt;However, on HP-UX it only seems to work with raw I/O, i.e. writing to raw devices, which at its downside may increase the administrative overhead.&lt;BR /&gt;From our Oracle DBA, who has access to the so called Oracle Metalink knowledge base, I was given a document that deals on this topic whose ID was "Metalink No. 139272.1".&lt;BR /&gt;I am uncertain about copyright issues why I refrain from attaching the doc to my reply.&lt;BR /&gt;Maybe you can find someone at your site who can browse the Oracle Metalinks?&lt;BR /&gt;The prevelance of async I/O may be detected by the existence of an async I/O device and Oracle DB writer processes which access it.&lt;BR /&gt;Since we are only using cooked I/O with our Oracle DB servers (our clients demand that) but all of our Informix DB servers are using it I can only demonstrate for an Informix box .&lt;BR /&gt;&lt;BR /&gt;e.g.&lt;BR /&gt;&lt;BR /&gt;# ll /dev/async*&lt;BR /&gt;crw-rw-rw-   1 bin        bin        101 0x000000 Dec  2  2005 /dev/async&lt;BR /&gt;crw-rw-rw-   1 bin        bin        101 0x000000 Dec  2  2005 /dev/asyncdsk&lt;BR /&gt; &lt;BR /&gt;# ps -fp "$(fuser -u /dev/async 2&amp;gt;/dev/null)"&lt;BR /&gt;ps: wrong PID number&lt;BR /&gt;     UID   PID  PPID  C    STIME TTY       TIME COMMAND&lt;BR /&gt;informix 29952 29951  0  Jan  8  ?         4:52 /opt/inf_99/bin/oninit -v&lt;BR /&gt;    root  1945     1  0  Dec 28  ?        200:55 /opt/inf_96/bin/oninit -v&lt;BR /&gt;    root  1947  1946  0  Dec 28  ?        72:37 /opt/inf_96/bin/oninit -v&lt;BR /&gt;informix  1812     1  0  Jan  8  ?        219:56 /opt/inf_altdb/bin/oninit -v&lt;BR /&gt;    root  1961     1  0  Dec 28  ?        44:49 /opt/inf_97/bin/oninit -v&lt;BR /&gt;    root  1964  1963  0  Dec 28  ?        53:46 /opt/inf_97/bin/oninit -v&lt;BR /&gt;informix 29950     1  0  Jan  8  ?        20:33 /opt/inf_99/bin/oninit -v&lt;BR /&gt;informix  1818  1813  0  Jan  8  ?        240:09 /opt/inf_altdb/bin/oninit -v&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;As you can see with Informix the crucial DB processes are called oninit.&lt;BR /&gt;&lt;BR /&gt;You can also check for the existence of the async driver in your running kernel.&lt;BR /&gt;  &lt;BR /&gt;# strings /stand/vmunix|grep async&lt;BR /&gt;fs_async&lt;BR /&gt;max_async_ports&lt;BR /&gt;Maximum Number of asyncdsk Ports That Can be Open At One Time&lt;BR /&gt;asyncdsk&lt;BR /&gt;asyncdsk_included&lt;BR /&gt;fs_async        1&lt;BR /&gt;asyncdsk_included&lt;BR /&gt;asyncdsk&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;# lsdev -d asyncdsk&lt;BR /&gt;    Character     Block       Driver          Class&lt;BR /&gt;      101          -1         asyncdsk        pseudo&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;And last but not least, a couple of async I/O related kernel tunable must be set, like these:&lt;BR /&gt; &lt;BR /&gt;# kmtune -q fs_async -q max_async_ports&lt;BR /&gt;Parameter             Current Dyn Planned                    Module     Version&lt;BR /&gt;===============================================================================&lt;BR /&gt;fs_async                    1  -  1&lt;BR /&gt;max_async_ports            50  -  50&lt;BR /&gt; &lt;BR /&gt;# kmtune|grep aio&lt;BR /&gt;aio_listio_max            256  -  256&lt;BR /&gt;aio_max_ops              2048  -  2048&lt;BR /&gt;aio_physmem_pct            10  -  10&lt;BR /&gt;aio_prio_delta_max         20  -  20</description>
      <pubDate>Tue, 06 Feb 2007 03:49:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938857#M762855</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2007-02-06T03:49:57Z</dc:date>
    </item>
    <item>
      <title>Re: Async IO is NOT ??</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938858#M762856</link>
      <description># strings /stand/vmunix|grep async&lt;BR /&gt;asyncdsk&lt;BR /&gt;asyncdsk_install&lt;BR /&gt;Maximum number of async IO operations that can be specified in lio_list call&lt;BR /&gt;Maximum number of async IO operations that can be queued at any time&lt;BR /&gt;Greatest delta (slowdown factor) allowed in async IO request priorities&lt;BR /&gt;asyncdsk_open_ports&lt;BR /&gt;max_async_ports&lt;BR /&gt;Maximum number of open asyncdsk ports&lt;BR /&gt;fs_async_writes_on&lt;BR /&gt;fs_async&lt;BR /&gt;async_debug_symbols&lt;BR /&gt;# lsdev -d asyncdsk&lt;BR /&gt;    Character     Block       Driver          Class&lt;BR /&gt;      101          -1         asyncdsk        pseudo&lt;BR /&gt;# kmtune -q fs_async -q max_async_ports&lt;BR /&gt;kmtune is a wrapper script which exists for compatibility reasons only.&lt;BR /&gt;The underlying command used is 'kctune'.  New or modified scripts or&lt;BR /&gt;procedures should use kctune directly.&lt;BR /&gt;About to execute: kctune    -q fs_async -q max_async_ports&lt;BR /&gt;Tunable          Value  Expression&lt;BR /&gt;fs_async             0  Default&lt;BR /&gt;max_async_ports     50  Default&lt;BR /&gt;#</description>
      <pubDate>Tue, 06 Feb 2007 05:03:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938858#M762856</guid>
      <dc:creator>Deep C Pandey</dc:creator>
      <dc:date>2007-02-06T05:03:11Z</dc:date>
    </item>
    <item>
      <title>Re: Async IO is NOT ??</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938859#M762857</link>
      <description>No, you don't seem to have fs_async support enabled in your kernel.&lt;BR /&gt;The mentioned Oracle Metalink describes exactly the steps needed to enable async I/O for Oracle.&lt;BR /&gt;&lt;BR /&gt;HTH</description>
      <pubDate>Tue, 06 Feb 2007 06:13:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/async-io-is-not/m-p/3938859#M762857</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2007-02-06T06:13:25Z</dc:date>
    </item>
  </channel>
</rss>

