<?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 max_queue_depth setting and oracle in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885526#M280643</link>
    <description>Group,&lt;BR /&gt;&lt;BR /&gt;Hey - I've just discovered the max_queue_depth setting and it's relationship to the EVA we have. I'm playing around with some scenarios and had a thought.&lt;BR /&gt;&lt;BR /&gt;If I make changes to the max queue depth on the luns that our oracle database uses, do changes need to be made within oracle to take advantage of the new max queue depth?  Or is this simply how many I/O requests the OS will throw at the lun?&lt;BR /&gt;&lt;BR /&gt;One reason that I ask, and I realize this is not a "normal" database function, but I doubled the queue depth on the luns used during the oracle hot backup and only saw minimal increases in the IO rate.  This should have been a good spot to test in my opinion.  I was hoping to see the IO rate really jump.  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I appreciate your feedback.&lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;&lt;BR /&gt;Charlie</description>
    <pubDate>Tue, 24 Oct 2006 07:42:34 GMT</pubDate>
    <dc:creator>Charles McCary</dc:creator>
    <dc:date>2006-10-24T07:42:34Z</dc:date>
    <item>
      <title>max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885526#M280643</link>
      <description>Group,&lt;BR /&gt;&lt;BR /&gt;Hey - I've just discovered the max_queue_depth setting and it's relationship to the EVA we have. I'm playing around with some scenarios and had a thought.&lt;BR /&gt;&lt;BR /&gt;If I make changes to the max queue depth on the luns that our oracle database uses, do changes need to be made within oracle to take advantage of the new max queue depth?  Or is this simply how many I/O requests the OS will throw at the lun?&lt;BR /&gt;&lt;BR /&gt;One reason that I ask, and I realize this is not a "normal" database function, but I doubled the queue depth on the luns used during the oracle hot backup and only saw minimal increases in the IO rate.  This should have been a good spot to test in my opinion.  I was hoping to see the IO rate really jump.  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I appreciate your feedback.&lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;&lt;BR /&gt;Charlie</description>
      <pubDate>Tue, 24 Oct 2006 07:42:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885526#M280643</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2006-10-24T07:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885527#M280644</link>
      <description>Hi Charlie,&lt;BR /&gt;&lt;BR /&gt;My gut feeling is that the new max_queue_depth will take effect immediately.  Maybe someone else could confirm.&lt;BR /&gt;&lt;BR /&gt;PCS</description>
      <pubDate>Tue, 24 Oct 2006 08:18:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885527#M280644</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-10-24T08:18:29Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885528#M280645</link>
      <description>Yes, if you change max_queue_depth with scsictl command the new value will take effect immediately. However, the value with be set back to original one after the server reboot.&lt;BR /&gt;&lt;BR /&gt;Yang</description>
      <pubDate>Tue, 24 Oct 2006 08:43:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885528#M280645</guid>
      <dc:creator>Yang Qin_1</dc:creator>
      <dc:date>2006-10-24T08:43:55Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885529#M280646</link>
      <description>Sorry...guess I didn't make myself clear.&lt;BR /&gt;&lt;BR /&gt;I understand the the effect is immediate.  &lt;BR /&gt;&lt;BR /&gt;My question has to do with oracle and if changes need to be made in the oracle configuration to take advantage of the new max_queue_depth.&lt;BR /&gt;&lt;BR /&gt;Also, if anyone has any ideas on why I didn't see a big jump in IO rate when I changed the luns used by the oracle backup.&lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;&lt;BR /&gt;Charlie</description>
      <pubDate>Tue, 24 Oct 2006 08:57:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885529#M280646</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2006-10-24T08:57:54Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885530#M280647</link>
      <description>Charlie,&lt;BR /&gt;&lt;BR /&gt;That is what I meant by "will take effect immediately".  In other words, no changes need to be made to Oracle configuration.&lt;BR /&gt;&lt;BR /&gt;As for the minimal increase in IO, I believe you're past the point of diminishing returns for max_queue_depth.&lt;BR /&gt;&lt;BR /&gt;PCS</description>
      <pubDate>Tue, 24 Oct 2006 09:06:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885530#M280647</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-10-24T09:06:13Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885531#M280648</link>
      <description>Point taken.&lt;BR /&gt;&lt;BR /&gt;How does one go about knowing when they are "past the point of diminishing returns", ie how can I verify this?</description>
      <pubDate>Tue, 24 Oct 2006 09:11:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885531#M280648</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2006-10-24T09:11:47Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885532#M280649</link>
      <description>What was your max_queue_depth anyway and to what value did you change it to?&lt;BR /&gt;&lt;BR /&gt;Our experience with Oracle on large EVA5K LUNs show that a qdepth setting of 64-128 is optimal.&lt;BR /&gt;&lt;BR /&gt;BTW, you will not see the immediate returns of tuning qdepth in a hotbackup scenario... You will see it in terms of how well your database will now be able to scale - i.e. more queries -- leading to overall faster performance...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Oct 2006 09:44:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885532#M280649</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2006-10-24T09:44:15Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885533#M280650</link>
      <description>Hi - it's an eva3000 and all queue depths were set to the default of 8.&lt;BR /&gt;&lt;BR /&gt;I changed them on these 3 luns to 16, as a test.&lt;BR /&gt;&lt;BR /&gt;I'd love to be able to set them all to 64, but I'm running in to the 2048 limit on the EVA.  We have some large luns and some smaller.  &lt;BR /&gt;&lt;BR /&gt;Do you think just changing the larger luns to 64 would be more effective than changing all the luns to 16 or so?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Oct 2006 09:50:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885533#M280650</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2006-10-24T09:50:34Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885534#M280651</link>
      <description>Hi Charlie,&lt;BR /&gt;&lt;BR /&gt;You should be able to glean a recommended value from the EVA documentation.  I would perform standard benchmarking to determine where the rate of increased IO performance is at a maximum.  That is, set max_queue_depth to a low value, benchmark, increase max_queue_depth, benchmark again, etc.&lt;BR /&gt;&lt;BR /&gt;PCS</description>
      <pubDate>Tue, 24 Oct 2006 09:53:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885534#M280651</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-10-24T09:53:56Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885535#M280652</link>
      <description>Charles, depending on how many of your connected servers are active at the same time (or how many of your LUNS will be active at the same time) -- I think it is safe to bump it up to a higher value.&lt;BR /&gt;&lt;BR /&gt;And even if it did reach the 2048 q limit, I don't think it will have serious repercussions to all your connected servers as they will just have an IO Wait on queuing...&lt;BR /&gt;&lt;BR /&gt;Just some thoughts...</description>
      <pubDate>Tue, 24 Oct 2006 10:02:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885535#M280652</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2006-10-24T10:02:17Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885536#M280653</link>
      <description>Nelson,&lt;BR /&gt;&lt;BR /&gt;HP was pretty conservative about not crossing the 2048 barrier.  I understand where you're coming from though.&lt;BR /&gt;&lt;BR /&gt;FYI, we're using securepath and here's an example of one of the luns using spmgr display:&lt;BR /&gt;&lt;BR /&gt;Here's an example of spmgr display output for one of the luns:&lt;BR /&gt;&lt;BR /&gt; TGT/LUN   Device             WWLUN_ID             H/W_Path           #_Paths&lt;BR /&gt;    3/  6   c13t3d6            6005-08B4-0010-23BC-0000-A000-004A-0000   4&lt;BR /&gt;                                                    255/255/0/3.6&lt;BR /&gt;          Controller  Path_Instance      HBA             Preferred?  Path_Status&lt;BR /&gt;          P66C5E2AAQT02B                                     no&lt;BR /&gt;                      c17t3d7            td1             YES          Active&lt;BR /&gt;                      c7t3d7             td0             YES          Active&lt;BR /&gt;&lt;BR /&gt;          Controller  Path_Instance      HBA             Preferred?  Path_Status&lt;BR /&gt;          P66C5E2AAQT016                                     no&lt;BR /&gt;                      c5t3d7             td0             no           Standby&lt;BR /&gt;                      c15t3d7            td1             no           Standby &lt;BR /&gt;</description>
      <pubDate>Tue, 24 Oct 2006 10:19:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885536#M280653</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2006-10-24T10:19:28Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885537#M280654</link>
      <description>Nelson,&lt;BR /&gt;&lt;BR /&gt;Also, when you say "active", do you mean:&lt;BR /&gt;&lt;BR /&gt;1) has an lvol and fs mounted on it.&lt;BR /&gt;&lt;BR /&gt;or &lt;BR /&gt;&lt;BR /&gt;2) has an lvol and fs mounted on it and is actively being read/written from/to.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I would say all of our luns meet 1 all of the time.&lt;BR /&gt;&lt;BR /&gt;I would say that there are times when 2 is the case as well.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Oct 2006 10:21:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885537#M280654</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2006-10-24T10:21:53Z</dc:date>
    </item>
    <item>
      <title>Re: max_queue_depth setting and oracle</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885538#M280655</link>
      <description>Charles, I would say (2)...</description>
      <pubDate>Tue, 24 Oct 2006 11:28:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/max-queue-depth-setting-and-oracle/m-p/3885538#M280655</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2006-10-24T11:28:20Z</dc:date>
    </item>
  </channel>
</rss>

