- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- BIOS setting on CPU performance
ProLiant Servers (ML,DL,SL)
1820485
Members
2407
Online
109624
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2004 01:41 AM
06-18-2004 01:41 AM
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...
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2004 03:57 AM
06-18-2004 03:57 AM
Solution
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.
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.
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.
Your mileage may vary.
Thanks,
Doug
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.
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.
Your mileage may vary.
Thanks,
Doug
I am an HPE employee

The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP