<?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: BIOS setting on CPU performance in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-setting-on-cpu-performance/m-p/3309213#M31452</link>
    <description>Basically it changes the way that the processors use the memory pre-fetch queue in cache.  In normal operations, if there is a memory cache hit, the processor may also do a pre-fetch of the next or adjacent memory location in the cache, which goes out to main memory for the fetch.  In heavy memory intensive applications, this maintains optimum performance. But in a lot of cases, the pre-fetched memory ends up being discarded anyways.&lt;BR /&gt;&lt;BR /&gt;However, in some cases where there is a lot of I/O, the memory pre-fetching, since it uses the same bus and bridge that PCI uses, can take up bus bandwidth that could be used by the I/O devices. Since much of the pre-fetched data is discarded anyways, turning off the pre-fetching frees up bus bandwidth for the I/O devices, and really doesn't impact memory performance.&lt;BR /&gt;&lt;BR /&gt;So the bottom line is that the default setting is optimized for memory, and HP recommends that you only change it if you have done your own benchmarking that indicates that it would increase overall system performance - with your application.  Databases could potentially benefit from the I/O setting, but you really need to test it with your specific environment. We have seen some improvement in TPC-C benchmarks using the I/O setting.&lt;BR /&gt;&lt;BR /&gt;Your mileage may vary.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Doug&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 18 Jun 2004 10:57:03 GMT</pubDate>
    <dc:creator>Doug de Werd</dc:creator>
    <dc:date>2004-06-18T10:57:03Z</dc:date>
    <item>
      <title>BIOS setting on CPU performance</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-setting-on-cpu-performance/m-p/3309212#M31451</link>
      <description>I noticed in the BIOS on a new DL580G3 the option to optimize the processor for 'memory' or for 'i/o'... We run some intense database stuff so I was interested when I saw I could 'optimize' for i/o instead of the default, which is memory, i'm wondering if anyone knows anything else about this setting, what it actually does and such...</description>
      <pubDate>Fri, 18 Jun 2004 08:41:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-setting-on-cpu-performance/m-p/3309212#M31451</guid>
      <dc:creator>Tim Allen_5</dc:creator>
      <dc:date>2004-06-18T08:41:26Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS setting on CPU performance</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-setting-on-cpu-performance/m-p/3309213#M31452</link>
      <description>Basically it changes the way that the processors use the memory pre-fetch queue in cache.  In normal operations, if there is a memory cache hit, the processor may also do a pre-fetch of the next or adjacent memory location in the cache, which goes out to main memory for the fetch.  In heavy memory intensive applications, this maintains optimum performance. But in a lot of cases, the pre-fetched memory ends up being discarded anyways.&lt;BR /&gt;&lt;BR /&gt;However, in some cases where there is a lot of I/O, the memory pre-fetching, since it uses the same bus and bridge that PCI uses, can take up bus bandwidth that could be used by the I/O devices. Since much of the pre-fetched data is discarded anyways, turning off the pre-fetching frees up bus bandwidth for the I/O devices, and really doesn't impact memory performance.&lt;BR /&gt;&lt;BR /&gt;So the bottom line is that the default setting is optimized for memory, and HP recommends that you only change it if you have done your own benchmarking that indicates that it would increase overall system performance - with your application.  Databases could potentially benefit from the I/O setting, but you really need to test it with your specific environment. We have seen some improvement in TPC-C benchmarks using the I/O setting.&lt;BR /&gt;&lt;BR /&gt;Your mileage may vary.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Doug&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Jun 2004 10:57:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-setting-on-cpu-performance/m-p/3309213#M31452</guid>
      <dc:creator>Doug de Werd</dc:creator>
      <dc:date>2004-06-18T10:57:03Z</dc:date>
    </item>
  </channel>
</rss>

