<?xml version="1.0"?>
<!DOCTYPE flagsdescription SYSTEM "http://www.spec.org/dtd/cpuflags2.dtd">

<flagsdescription>

<filename>HPE-Platform-Flags-Intel-V1.2-HSW-revG</filename>

<title>SPEC CPU2006 Platform Settings for HP Proliant Intel-based systems</title>

<os_tuning>
<![CDATA[

<p><b>OS Tuning</b></p>

<p><b>Drive Write Cache</b></p>
<p>The Drive Write Cache is an option that can be enabled or disabled in the HP Array Configuration Utility, CLI version. The default value for the Drive Write Cache is set to Disabled, and in order to change this the HP Array Configuration Utility, CLI version needs to be installed. When the Drive Write Cache option is enabled on a HP Smart Array Controller in a system, it can allow the HP Smart	Array Controller to help make drive writes more efficient.</p>

<p><b>Accelerator Ratio</b></p>
<p>The Accelerator Ratio is an option that can be set to different percentages (in 25% increments) in the HP Array Configuration Utility, CLI version. The default value for the Accelerator Ratio is set to 0% Read and 100% Write. In order to change this the HP Array Configuration Utility, CLI version needs to be installed. Changing the Accelerator Ratio allows the array installed on the HP Smart Array Controller to adjust how the priority of reads and writes.</p>

<p><b> ulimit -s [n | unlimited] (Linux) </b></p>
<p>Sets the stack size to <b>n</b> kbytes, or <b>unlimited</b> to allow the stack size to grow without limit. </p>

<p><b> vm.max_map_count-n (Linux) </b></p>
<p>The maximum number of memory map areas a process may have. Memory map areas are used as a side-effect of calling malloc, directly by mmap and mprotect, and also when loading shared libraries. </p>

<p><b> Zone Reclaim: </b></p>
<p> Zone reclaim allows the reclaiming of pages from a zone if the number of free pages falls below a watermark even if other zones still have enough pages available. Reclaiming a page can be more beneficial than taking the performance penalties that are associated with allocating a page on a remote zone, especially for NUMA machines.</p>

<p><b> Disabled unused Linux services via stop_services.sh script.</b></p>
<p>The following unused Linux services were disabled before the run in simple shell scirpt via the command "service {name} stop":
 abrt-ccpp, abrt-oops, abrtd, acpid, atd, auditd, autofs, avahi-daemon, cgconfig, cpuspeed, crond, cups, haldaemon, irqbalance, kdump, libvirt-guests, mcelogd, mdmonitor,   messagebus, portreserve, postfix, rhnsd, rhsmcertd, rpcbind, rpcgssd, rpcidmapd, certmonger, lvm2-monitor, netfs, and sysstat.</p>
]]>
</os_tuning>

<firmware>
<![CDATA[

<p><b>Firmware Settings</b></p>

<p>One or more of the following settings may have been set.  If so, the "Platform Notes" section of the
report will say so; and you can read below to find out more about what these settings mean.</p>

<p><b>Intel Hyperthreading Options (Default = Enabled):</b></p> 
<p>This feature allows enabling/disabling of logical processor cores on processors supporting Intel's Hyperthreading Technology.  When enabled,
each physical processor core operates as two logical processor cores. When disabled, each physical core operates as only one logical processor 
core. Enabling this option can improve overall performance for applications that benefit from a higher processor core count.</p>

<p><b>HP Power Profile (Default = Balanced Power and Performance):</b></p>
<p> Values for this BIOS setting can be:</p>
<ul>
<li><b>Balanced Power and Performance</b>: Provides the optimum settings to maximize power savings with minimal impact to performance for most 
operating systems and applications.</li>
<li><b>Minimum Power Usage</b>: Enables power reduction mechanisms that may negatively affect performance. This mode guarantees a lower maximum power usage by the system.</li> 
<li><b>Maximum Performance</b>: Disables all power management options that may negatively affect performance.</li>
<li><b>Custom</b>:Allows the user to customize power management options independent of the defaults that each preset Power Profile sets.</li>
</ul>

<p><b>HP Power Regulator (Default = HP Dynamic Power Savings Mode)</b></p> 
<p>This option can only be configured if the HP Power Profile is set to Custom. Values for this BIOS setting can be:</p>
<ul> 
<li><b>HP Dynamic Power Savings Mode</b>: Automatically varies processor speed and power usage based on processor utilization. Allows reducing 
overall power consumption with little or no impact to performance. Does not require OS support. </li>
<li><b>HP Static Low Power Mode</b>: Reduces processor speed and power usage. Guarantees a lower maximum power usage for the system. Performance impacts will be greater for environments with higher processor utilization. </li>
<li><b>HP Static High Performance Mode</b>: Processors will run in their maximum power/performance state at all times regardless of the OS power management policy. </li>
<li><b>OS Control Mode</b>: Processors will run in their maximum power performance state at all times unless the OS enables a power management policy. </li>
</ul>

<p><b>Minimum Processor Idle Power Core C-State (Default = C6 State):</b></p>
<p>This option can only be configured if the HP Power Profile is set to Custom. This feature selects the processor's lowest idle core power state
(C-state) that the operating system uses. The higher the C-state, the lower the power usage of that idle state (C6 is the lowest power idle state supported by the processor). Values for this setting can be:</p>
<ul>
<li><b>C6 State</b>: While in C6, the core PLLs are turned off, the core caches are flushed and the core state is saved to the Last Level Cache. Power Gates are used to reduce power consumption to close to zero.  C6 is considered an inactive core.</li>
<li><b>C3 State</b>: While in C3 the core PLLs are turned off, and all the core caches are flushed.  C3 is considered an inactive core.</li>
<li><b>C1E State</b>: C1E is defined as the enhanced halt state.  While in C1E no instructions are being executed.  C1E considered an active core. </li>
<li><b>No C-states</b>: No C-states is defined as C0, which is defined as the active state. While in C0, instructions are being executed by the core.</li>
</ul>

<p><b>Minimum Processor Idle Power Package C-State (Default = Package C6(retention) State):</b></p>
<p>This option can only be configured if the HP Power Profile is set to Custom. This feature selects the processor's lowest idle package power state (C-state) that is enabled.  The processor will automatically transition into the package C-states based on the Core C-states, in which cores on the processor have transitioned.  The higher the package C-state, the lower the power usage of that idle package state (Package C6(retention) is the lowed power idle package state supported by the processor). Values for this setting can be:</p>
<ul>
<li><b>Package C6 (retention) State</b>: All cores have saved their architectural state and have had their core voltages reduced to zero volts. The LLC retains context, but no accesses can be made to the LLC in this state, the cores must break out to the internal state package C2 for snoops to occur.</li>
<li><b>Package C6 (non-retention) State</b>: All cores have saved their architectural state and have had their core voltages reduced to zero volts. The LLC does not retain context, and no accesses can be made to the LLC in this state, the cores must break out to the internal state package C2 for snoops to occur.</li>
<li><b>No Package State</b>: All cores are in an active state and have not entered any power saving state.</li>
</ul>

<p><b>Energy/Performance Bias (Default = Balanced Performance):</b></p>
<p>This option can only be configured if the HP Power Profile is set to Custom. This option configures several processor subsystems to optimize the processor's performance and power usage. Values for this BIOS setting can be:</p>
<ul>
<li><b>Balanced Performance</b>: Provides optimum performance efficiency and is recommended for most environments.</li>
<li><b>Maximum Performance Mode</b>: Should be used for environments that require the highes performance and lowest latency but are not sensitive to power consumption.</li>  
<li><b>Balanced Power</b>: Provides optimum power efficiency</li>
<li><b>Power Savings Mode</b>: Should only be used in environments that are power sensitive and are willing to accept reduced performance.</li>
</ul>

<p><b>Collaborative Power Control (Default = Enabled):</b></p> 
<p>This BIOS option allows the enabling/disabling of the Processor Clocking Control (PCC) Interface, for operating systems which support this feature.  Enabling this option allows the Operating System to request processor frequency changes even when the server has the Power Regulator option configured for Dynamic Power Savings Mode.</p>
<p>For Operating Systems that do not support the PCC Interface or when the Power Regulator Mode is not configured for Dynamic Power Savings Mode, his option has no impact on system operation.</p>

<p><b>QPI Snoop Configuration (Default = Home Snoop):</b></p>
<p>This option allows the user to choose the snoop mode used by the processor and QPI (Quick Path Interconnect) bus. Snooping is a process where the individual caches monitor address lines for accesses to memory locations that have cached. Changing this option can have an impact on memory performance. The performance of various workloads will vary depending on the mode selected and the order in which they are listed here does not reflect any technical ordering or ranking. The order seen here reflects the order as currently seen in the BIOS. Values for this setting can be:</p>
<ul>
<li><b>Home Snoop</b>: The snoop is always spawned by the home agent in this mode. This mode is best for workloads that are bandwidth sensitive and need maximum local and remote memory bandwidth. This mode provides high memory bandwidth in an average NUMA environment.</li>
<li><b>Early Snoop</b>: Since the snoop is sent from the caching agent, this mode has lower latency vs. Home Snoop mode. This mode is best for workloads that are latency sensitive, or workloads that benefit from fast cache-to-cache transfer latencies from the remote socket. This mode will decrease memory latency but may also result in lower overall bandwidth as compared to the other modes.</li>
<li><b>Cluster on Die</b>: This mode logically splits a socket into 2 NUMA domains that are exposed to the OS. Each NUMA domain has half the cores, last level cache and one home agent with an equal number of cache slices in each NUMA domain. A directory cache in the home agent is used along with in memory directory bits to determine whether a snoop needs to be sent from the home agent. This mode has the best local latency and local memory bandwidth and is best for highly NUMA optimized workloads. This mode reduces average last level cache hit and local memory latencies.
Although selectable in unsupported configurations, Cluster on Die will be set and occur only when a system has one socket and two socket processors SKUs with two Home Agents (ex. E5-2600 v3 processors with 10+ cores). On an HP ProLiant Gen9 system, when selecting Cluster on Die with a processor that doesn't support this mode, the QPI Snoop Configuration will fall back to Home Snoop.</li>
</ul>

<p><b>NUMA Group Size Optimization (Default = Clustered):</b></p>
<p>This feature allows the user to configure how the BIOS reports the size of a NUMA node (number of logical processors), which assists the Operating System in grouping processors for application use (referred to as Kgroups). Values for this BIOS option can be:</p>
<ul>
<li><b>Clustered</b>: Might provide better performance for some workloads due to optimizing the resulting groups along NUMA boundaries.</li>
<li><b>Flat</b>: Might provide better performance for some workloads that cannot take advantage of processors spanning multiple groups. This setting would be necessary to help this class of applications utilize more logical processors.</li>
</ul>

<p><b>Thermal Configuration (Default = Optimal Cooling):</b></p>
<p>This feature allows the user to select the fan cooling solution for the system. Values for this BIOS option can be:</p>
<ul>
<li><b>Optimal Cooling</b>: Provides the most efficient solution by configuring fan speeds to the minimum required to provide adequate cooling.</li>
<li><b>Increased Cooling</b>: Will run fans at higher speeds to provide additional cooling. Increased Cooling should be selected when non-HP storage controllers are cabled to the embedded hard drive cage, or if the system is experiencing thermal issues that cannot be resolved in another manner.</li>
<li><b>Maximum Cooling</b>: Will provide the maximum cooling available by this platform.</li>
</ul>

<p><b>Processor Power and Utilization Monitoring (Default = Enabled):</b></p>
<p>This BIOS option allows the enabling/disabling of iLo Processor State Mode Switching and Insight Power Management Processor Utilization Monitoring.</p>
<p>When set to disabled, the system will also set the HP Power Regulator mode to HP Static High Performance mode and the HP Power Profile mode to Custom.  This option may be useful in some environments that require absolute minimum latency.</p>

<p><b>Memory Patrol Scrubbing (Default = Enabled):</b></p>
<p>This BIOS option allows the enabling/disabling of Memory Periodic Patrol Scrubber. The Memory Periodic Patrol Scrubber corrects memory soft errors so that, over the length of the system runtime, the risk of producing multi-bit and uncorrectable errors is reduced.</p>

<p><b>Memory Refresh Rate (Default = 2x Refresh):</b></p>
<p>This BIOS option controls the refresh rate of the memory controller and may affect the performance and resiliency of the servers memory.</p>
<p>When set to 1x Refresh, the memory refresh rate will be decreased, the HP Power Regulator mode will be set to HP Static High Performance mode, and the HP Power Profile mode to Custom.  This option may be useful in some environments that require absolute minimum latency.</p>
<p>When set to 3x Refresh, the memory refresh rate will be increased, the HP Power Regulator mode will be set to HP Static High Performance mode, and the HP Power Profile mode to Custom.</p>

<p><b>Last updated October 17th, 2014.</b></p>
]]>
</firmware>

</flagsdescription>