<?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: Number Of Requests Key in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/number-of-requests-key/m-p/4114268#M25657</link>
    <description>&lt;!--!*#--&gt;We never found an answer and left it as is. It may have been a bit of a red herring, because the reg key wasn't on our server (maybe you need to create it?) and few people had heard of it. Here's a dump of our notes on it, if it's any help:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;INCREASE NUMBEROFREQUESTS / QUEUDEPTH?&lt;BR /&gt;&lt;BR /&gt;    &lt;A href="http://www.microsoft.com/whdc/device/storage/subsys_perf.mspx" target="_blank"&gt;http://www.microsoft.com/whdc/device/storage/subsys_perf.mspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;        "Both SCSIport and Storport miniport drivers can use a&lt;BR /&gt;        registry parameter to designate how much concurrency is&lt;BR /&gt;        allowed on a device by device basis. The default is 16,&lt;BR /&gt;        which is much too small for a storage subsystem of any&lt;BR /&gt;        decent size unless quite a number of physical disks are&lt;BR /&gt;        being presented to the operating system by the controller.&lt;BR /&gt;        The maximum value is 255, but this is probably excessive&lt;BR /&gt;        in most configurations. Increasing the value beyond the&lt;BR /&gt;        needed amount results in wasted memory (that is, increased&lt;BR /&gt;        memory footprint)."&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;    &lt;A href="http://technet.microsoft.com/en-us/library/bb463205.aspx" target="_blank"&gt;http://technet.microsoft.com/en-us/library/bb463205.aspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;        This parameter allows you to specify the number of SRBs created&lt;BR /&gt;        for a given adapter. This improves performance and allows Windows&lt;BR /&gt;        to give more disk requests to a logical disk, which is most useful&lt;BR /&gt;        for HW RAID adapters that have concurrency capabilities, because&lt;BR /&gt;        each logical disk consists of multiple physical disks. However,&lt;BR /&gt;        the default setting is often less than optimal for many high-speed&lt;BR /&gt;        HW RAID disk arrays. Overall disk array performance can be&lt;BR /&gt;        improved by setting NumberOfRequests to a value in the range of 32&lt;BR /&gt;        to 96 (decimal). Set the following registry entry:&lt;BR /&gt;&lt;BR /&gt;        HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MINIPORT_ADAPTER\Parameters\DeviceN\NumberOfRequests (REG_DWORD)&lt;BR /&gt;&lt;BR /&gt;        Replace miniport_adapter with the specific adapter name. Make an&lt;BR /&gt;        entry for each device, and in each entry replace DeviceN with&lt;BR /&gt;        Device1, Device2, and so forth, depending on the number of devices&lt;BR /&gt;        you are adding. A reboot is required for this setting to take&lt;BR /&gt;        effect. For example, for two Emulex LP9000 miniport adapters whose&lt;BR /&gt;        miniport driver name is lp6nds35, you would create the following&lt;BR /&gt;        registry entries set to 96:&lt;BR /&gt;&lt;BR /&gt;        HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lp6nds35\Parameters\Device0\NumberOfRequests&lt;BR /&gt;        HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lp6nds35\Parameters\Device1\NumberOfRequests&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;    &lt;A href="http://www.microsoft.com/whdc/device/storage/RAID_design.mspx" target="_blank"&gt;http://www.microsoft.com/whdc/device/storage/RAID_design.mspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;        Designing RAID Adapters to Work with Windows&lt;BR /&gt;        ...&lt;BR /&gt;&lt;BR /&gt;        In addition, if a RAID miniport supports more than one outstanding&lt;BR /&gt;        request per logical unit (LU) or virtual disk, the miniport must&lt;BR /&gt;        control the queue depth.&lt;BR /&gt;        *   For SCSIport miniports, the NumberOfRequests registry setting&lt;BR /&gt;            controls the queue depth for the entire adapter.&lt;BR /&gt;        *   With Storport, the queue is per LU and the miniport must set&lt;BR /&gt;            the depth to an appropriate value by using&lt;BR /&gt;            StorPortSetDeviceQueueDepth. Storport miniports also can&lt;BR /&gt;            freeze and thaw the individual device queues or do so at the&lt;BR /&gt;            adapter level. (Storport does not use the NumberOfRequests&lt;BR /&gt;            setting.)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;    proper settings for p800 raid controller&lt;BR /&gt;&lt;BR /&gt;            reg key above doesn't exist on our server&lt;BR /&gt;            searched registry for 'numberofrequests', nothing&lt;BR /&gt;            found&lt;BR /&gt;&lt;BR /&gt;        can't find documentation anywhere re: concurrency or&lt;BR /&gt;        numberofrequests&lt;BR /&gt;            -   userguide&lt;BR /&gt;            -   tech brief&lt;BR /&gt;            -   quickspecs&lt;BR /&gt;            -   google&lt;BR /&gt;&lt;BR /&gt;        Jay at hp support:&lt;BR /&gt;        -   windows tech support&lt;BR /&gt;        -   talked to 5 storage support guys, nobody heard of&lt;BR /&gt;            numberofrequests&lt;BR /&gt;        -   if it worked as well as Microsoft says, we'd very likely&lt;BR /&gt;            already be using it&lt;BR /&gt;        -   can try a few different settings and see what results are&lt;BR /&gt;        .   proceed at own risk&lt;BR /&gt;&lt;BR /&gt;        google turns up a few reports of it being set to 80 by&lt;BR /&gt;        admins of hp servers, but not for our specific controller&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 19 Nov 2008 17:14:53 GMT</pubDate>
    <dc:creator>IntelInc</dc:creator>
    <dc:date>2008-11-19T17:14:53Z</dc:date>
    <item>
      <title>Number Of Requests Key</title>
      <link>https://community.hpe.com/t5/disk-enclosures/number-of-requests-key/m-p/4114266#M25655</link>
      <description>Does anyone know what the NumberOfRequests key should be set to for p800 SAS RAID controller? We have it installed on a ML350 G5, with six 15K 300GB SAS disks in a raid 1+0 config.&lt;BR /&gt;&lt;BR /&gt;These microsoft links, among others:&lt;BR /&gt;    &lt;A href="http://www.microsoft.com/whdc/device/storage/subsys_perf.mspx" target="_blank"&gt;http://www.microsoft.com/whdc/device/storage/subsys_perf.mspx&lt;/A&gt;&lt;BR /&gt;    &lt;A href="http://technet.microsoft.com/en-us/library/bb463205.aspx" target="_blank"&gt;http://technet.microsoft.com/en-us/library/bb463205.aspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;... say that the key controls the queue depth or number of concurrent requests to the controller, and that by default it's configured for low-end controllers. A p800 should be able to handle more, but how much more?&lt;BR /&gt;&lt;BR /&gt;The relevant key is&lt;BR /&gt;HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\&lt;MINIPORT_ADAPTER&gt;\Parameters\Device&lt;N&gt;\NumberOfRequests (REG_DWORD)&lt;BR /&gt;&lt;BR /&gt;A few posts of configuration files include the setting, but not for our hardware and there's no discussion of it.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;/N&gt;&lt;/MINIPORT_ADAPTER&gt;</description>
      <pubDate>Mon, 10 Dec 2007 15:06:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/number-of-requests-key/m-p/4114266#M25655</guid>
      <dc:creator>IntelInc</dc:creator>
      <dc:date>2007-12-10T15:06:00Z</dc:date>
    </item>
    <item>
      <title>Re: Number Of Requests Key</title>
      <link>https://community.hpe.com/t5/disk-enclosures/number-of-requests-key/m-p/4114267#M25656</link>
      <description>Did you ever get an answer to your question?  Have you played around the setting yourself at all?  I'm in the same boat.</description>
      <pubDate>Wed, 19 Nov 2008 15:11:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/number-of-requests-key/m-p/4114267#M25656</guid>
      <dc:creator>David J. Nelson</dc:creator>
      <dc:date>2008-11-19T15:11:11Z</dc:date>
    </item>
    <item>
      <title>Re: Number Of Requests Key</title>
      <link>https://community.hpe.com/t5/disk-enclosures/number-of-requests-key/m-p/4114268#M25657</link>
      <description>&lt;!--!*#--&gt;We never found an answer and left it as is. It may have been a bit of a red herring, because the reg key wasn't on our server (maybe you need to create it?) and few people had heard of it. Here's a dump of our notes on it, if it's any help:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;INCREASE NUMBEROFREQUESTS / QUEUDEPTH?&lt;BR /&gt;&lt;BR /&gt;    &lt;A href="http://www.microsoft.com/whdc/device/storage/subsys_perf.mspx" target="_blank"&gt;http://www.microsoft.com/whdc/device/storage/subsys_perf.mspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;        "Both SCSIport and Storport miniport drivers can use a&lt;BR /&gt;        registry parameter to designate how much concurrency is&lt;BR /&gt;        allowed on a device by device basis. The default is 16,&lt;BR /&gt;        which is much too small for a storage subsystem of any&lt;BR /&gt;        decent size unless quite a number of physical disks are&lt;BR /&gt;        being presented to the operating system by the controller.&lt;BR /&gt;        The maximum value is 255, but this is probably excessive&lt;BR /&gt;        in most configurations. Increasing the value beyond the&lt;BR /&gt;        needed amount results in wasted memory (that is, increased&lt;BR /&gt;        memory footprint)."&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;    &lt;A href="http://technet.microsoft.com/en-us/library/bb463205.aspx" target="_blank"&gt;http://technet.microsoft.com/en-us/library/bb463205.aspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;        This parameter allows you to specify the number of SRBs created&lt;BR /&gt;        for a given adapter. This improves performance and allows Windows&lt;BR /&gt;        to give more disk requests to a logical disk, which is most useful&lt;BR /&gt;        for HW RAID adapters that have concurrency capabilities, because&lt;BR /&gt;        each logical disk consists of multiple physical disks. However,&lt;BR /&gt;        the default setting is often less than optimal for many high-speed&lt;BR /&gt;        HW RAID disk arrays. Overall disk array performance can be&lt;BR /&gt;        improved by setting NumberOfRequests to a value in the range of 32&lt;BR /&gt;        to 96 (decimal). Set the following registry entry:&lt;BR /&gt;&lt;BR /&gt;        HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MINIPORT_ADAPTER\Parameters\DeviceN\NumberOfRequests (REG_DWORD)&lt;BR /&gt;&lt;BR /&gt;        Replace miniport_adapter with the specific adapter name. Make an&lt;BR /&gt;        entry for each device, and in each entry replace DeviceN with&lt;BR /&gt;        Device1, Device2, and so forth, depending on the number of devices&lt;BR /&gt;        you are adding. A reboot is required for this setting to take&lt;BR /&gt;        effect. For example, for two Emulex LP9000 miniport adapters whose&lt;BR /&gt;        miniport driver name is lp6nds35, you would create the following&lt;BR /&gt;        registry entries set to 96:&lt;BR /&gt;&lt;BR /&gt;        HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lp6nds35\Parameters\Device0\NumberOfRequests&lt;BR /&gt;        HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\lp6nds35\Parameters\Device1\NumberOfRequests&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;    &lt;A href="http://www.microsoft.com/whdc/device/storage/RAID_design.mspx" target="_blank"&gt;http://www.microsoft.com/whdc/device/storage/RAID_design.mspx&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;        Designing RAID Adapters to Work with Windows&lt;BR /&gt;        ...&lt;BR /&gt;&lt;BR /&gt;        In addition, if a RAID miniport supports more than one outstanding&lt;BR /&gt;        request per logical unit (LU) or virtual disk, the miniport must&lt;BR /&gt;        control the queue depth.&lt;BR /&gt;        *   For SCSIport miniports, the NumberOfRequests registry setting&lt;BR /&gt;            controls the queue depth for the entire adapter.&lt;BR /&gt;        *   With Storport, the queue is per LU and the miniport must set&lt;BR /&gt;            the depth to an appropriate value by using&lt;BR /&gt;            StorPortSetDeviceQueueDepth. Storport miniports also can&lt;BR /&gt;            freeze and thaw the individual device queues or do so at the&lt;BR /&gt;            adapter level. (Storport does not use the NumberOfRequests&lt;BR /&gt;            setting.)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;    proper settings for p800 raid controller&lt;BR /&gt;&lt;BR /&gt;            reg key above doesn't exist on our server&lt;BR /&gt;            searched registry for 'numberofrequests', nothing&lt;BR /&gt;            found&lt;BR /&gt;&lt;BR /&gt;        can't find documentation anywhere re: concurrency or&lt;BR /&gt;        numberofrequests&lt;BR /&gt;            -   userguide&lt;BR /&gt;            -   tech brief&lt;BR /&gt;            -   quickspecs&lt;BR /&gt;            -   google&lt;BR /&gt;&lt;BR /&gt;        Jay at hp support:&lt;BR /&gt;        -   windows tech support&lt;BR /&gt;        -   talked to 5 storage support guys, nobody heard of&lt;BR /&gt;            numberofrequests&lt;BR /&gt;        -   if it worked as well as Microsoft says, we'd very likely&lt;BR /&gt;            already be using it&lt;BR /&gt;        -   can try a few different settings and see what results are&lt;BR /&gt;        .   proceed at own risk&lt;BR /&gt;&lt;BR /&gt;        google turns up a few reports of it being set to 80 by&lt;BR /&gt;        admins of hp servers, but not for our specific controller&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Nov 2008 17:14:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/number-of-requests-key/m-p/4114268#M25657</guid>
      <dc:creator>IntelInc</dc:creator>
      <dc:date>2008-11-19T17:14:53Z</dc:date>
    </item>
  </channel>
</rss>

