<?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: max_q_depth escsi_maxphys in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482023#M362653</link>
    <description>Hi,&lt;BR /&gt;As in the scsimgr man page escsi_maxphys value is :Maximum I/O size allowed by he SCSI subsystem in 4KB units. So 512x4k=2MB.&lt;BR /&gt;&lt;BR /&gt;If you are using VXFS then you already have a limit of max 1MB IO, so it is not meaningfull to tune escsi_maxphys. If you are using disk as a raw devices, or LVM volumes as a raw devices, then you might gain some benefits when doing sequential IO.</description>
    <pubDate>Thu, 20 Aug 2009 06:42:42 GMT</pubDate>
    <dc:creator>Turgay Cavdar</dc:creator>
    <dc:date>2009-08-20T06:42:42Z</dc:date>
    <item>
      <title>max_q_depth escsi_maxphys</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482018#M362648</link>
      <description>We use 11.31 system in Superdome. we want to adjust max_q_depth escsi_maxphys parameter to get higher performance. But we don't know depend on what to change it and change to what value.&lt;BR /&gt;Could you help us, thanks.</description>
      <pubDate>Wed, 19 Aug 2009 03:53:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482018#M362648</guid>
      <dc:creator>xin_jerry</dc:creator>
      <dc:date>2009-08-19T03:53:56Z</dc:date>
    </item>
    <item>
      <title>Re: max_q_depth escsi_maxphys</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482019#M362649</link>
      <description>For max_q_depth and escsi_maxphys look at &lt;A href="http://docs.hp.com/en/11iv3IOPerf/IOPerformanceWhitePaper.pdf" target="_blank"&gt;http://docs.hp.com/en/11iv3IOPerf/IOPerformanceWhitePaper.pdf&lt;/A&gt; page 9.&lt;BR /&gt;&lt;BR /&gt;Generally storage providers/administrators tell us the optimum value for max_q_depth.</description>
      <pubDate>Wed, 19 Aug 2009 04:15:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482019#M362649</guid>
      <dc:creator>Turgay Cavdar</dc:creator>
      <dc:date>2009-08-19T04:15:24Z</dc:date>
    </item>
    <item>
      <title>Re: max_q_depth escsi_maxphys</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482020#M362650</link>
      <description>we changed the parameter as followed:&lt;BR /&gt;scsimgr save_attr â  a escsi_maxphys=1048575  &lt;BR /&gt; scsimgr save_attr â  a max_q_depth=64 â  D /dev/rdisk/**&lt;BR /&gt;&lt;BR /&gt;But the performance was bad,when press was heavy, it seemed good. whne the press was less, the process also runned slowly.&lt;BR /&gt;&lt;BR /&gt;Could any body tell me the usage of escsi_maxphys, and why need to modify it?&lt;BR /&gt;&lt;BR /&gt;thanks a lot</description>
      <pubDate>Thu, 20 Aug 2009 04:11:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482020#M362650</guid>
      <dc:creator>xin_jerry</dc:creator>
      <dc:date>2009-08-20T04:11:57Z</dc:date>
    </item>
    <item>
      <title>Re: max_q_depth escsi_maxphys</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482021#M362651</link>
      <description>&lt;!--!*#--&gt;Hi Jerry,&lt;BR /&gt;&lt;BR /&gt;escsi_maxphys: Maximum I/O size allowed by the SCSI subsystem in 4KB units. Range: 64 - 1048575&lt;BR /&gt;&lt;BR /&gt;Some of the many tunables that can be used for I/O performance are things like escsi_maxphys and the max_q_depth setting. escsi_maxphys controls the max I/O size and has been increased from 1 MB in 11i v2 to 2 MB in 11i v3. The use of a larger max I/O size allows for more efficient I/O performance for coallesced and sequential IOs. The max_q_depth setting is a key scsimgr attribute that allows for an increased number of concurrent I/Os to be issues on a per path basis. The defaiult max_q_depth value is set to eight, and with the use of larger LUN capacities, or even otherwise, a system admin may want to look at the max_q_depth settings and see if their environment can gain in performance from an increase of max_q_depth.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this makes things a bit clear..</description>
      <pubDate>Thu, 20 Aug 2009 04:42:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482021#M362651</guid>
      <dc:creator>R.K. #</dc:creator>
      <dc:date>2009-08-20T04:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: max_q_depth escsi_maxphys</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482022#M362652</link>
      <description>thanks for your reply.&lt;BR /&gt;escsi_maxphys controls the max I/O size and has been increased from 1 MB in 11i v2 to 2 MB in 11i v3. It's difficult to understand.&lt;BR /&gt;escsi_maxphys max value is 1048575. How it controls max I/O. escsi_maxphys default value is 512. If we use max value, what will happen to system?</description>
      <pubDate>Thu, 20 Aug 2009 06:04:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482022#M362652</guid>
      <dc:creator>xin_jerry</dc:creator>
      <dc:date>2009-08-20T06:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: max_q_depth escsi_maxphys</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482023#M362653</link>
      <description>Hi,&lt;BR /&gt;As in the scsimgr man page escsi_maxphys value is :Maximum I/O size allowed by he SCSI subsystem in 4KB units. So 512x4k=2MB.&lt;BR /&gt;&lt;BR /&gt;If you are using VXFS then you already have a limit of max 1MB IO, so it is not meaningfull to tune escsi_maxphys. If you are using disk as a raw devices, or LVM volumes as a raw devices, then you might gain some benefits when doing sequential IO.</description>
      <pubDate>Thu, 20 Aug 2009 06:42:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-q-depth-escsi-maxphys/m-p/4482023#M362653</guid>
      <dc:creator>Turgay Cavdar</dc:creator>
      <dc:date>2009-08-20T06:42:42Z</dc:date>
    </item>
  </channel>
</rss>

