<?xml version="1.0"?>

<!DOCTYPE flagsdescription SYSTEM "http://www.spec.org/dtd/cpuflags2.dtd">

<flagsdescription>

<filename>HPE-Platform-Flags-Intel-CatlowRefresh-rev1.1</filename>

<title>SPEC CPU2006/SPEC CPU2017 Platform Settings for HPE ProLiant Intel-based systems</title>

<os_tuning>
<![CDATA[

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

<p><b>ulimit</b>:</p>
<p>Used to set user limits of system-wide resources. Provides control over resources available to the shell and processes started by it. Some common ulimit commands may include:</p>
<ul>
<li><b>ulimit -s [n | unlimited]</b>: Set the stack size to <b>n</b> kbytes, or <b>unlimited</b> to allow the stack size to grow without limit.</li>
<li><b>ulimit -l (number)</b>: Set the maximum size that can be locked into memory.</li>
</ul>

<p><b>Disabling Linux services</b>:</p>
<p>Certain Linux services may be disabled to minimize tasks that may consume CPU cycles.</p>

<p><b>irqbalance</b>:</p>
<p>Disabled through "service irqbalance stop". Depending on the workload involved, the irqbalance service reassigns various IRQ's to system CPUs. Though this service might help in some situations, disabling it can also help environments which need to minimize or eliminate latency to more quickly respond to events.</p>

<p><b>Performance Governors (Linux)</b>:</p>
<p>In-kernel CPU frequency governors are pre-configured power schemes for the CPU. The CPUfreq governors use P-states to change frequencies and lower power consumption. The dynamic governors can switch between CPU frequencies, based on CPU utilization to allow for power savings while not sacrificing performance.</p>
<p>Other options beside a generic performance governor can be set, such as the perf-bias:</p>
<p><b>--perf-bias, -b</b></p>
<p>On supported Intel processors, this option sets a register which allows the cpupower utility (or other software/firmware) to set a policy that controls the relative importance of performance versus energy savings to the processor. The range of valid numbers is 0-15, where 0 is maximum performance and 15 is maximum energy efficiency.</p>
<p>The processor uses this information in model-specific ways when it must select trade-offs between performance and energy efficiency. This policy hint does not supersede Processor Performance states (P-states) or CPU Idle power states (C-states), but allows software to have influence where it would otherwise be unable to express a preference.</p>
<p>On many Linux systems one can set the perf-bias for all CPUs through the cpupower utility with one of the following commands:</p>
<ul>
<li>"cpupower -c all set -b 0"</li>
<li>"cpupower -c all set --perf-bias 0"</li>
<li>"cpupower set -b 0"</li>
</ul>

<p><b>Tuning Kernel parameters</b>:</p>
<p>The following Linux Kernel parameters were tuned to better optimize performance of some areas of the system:</p>
<ul>
<li><b>dirty_background_ratio</b>: Set through "echo 40 > /proc/sys/vm/dirty_background_ratio". This setting can help Linux disk caching and performance by setting the percentage of system memory that can be filled with dirty pages.</li>
<li><b>dirty_ratio</b>: Set through "echo 40 > /proc/sys/vm/dirty_ratio". This setting is the absolute maximum amount of system memory that can be filled with dirty pages before everything must get committed to disk.</li>
<li><b>swappiness</b>: The swappiness value can range from 1 to 100. A value of 100 will cause the kernel to swap out inactive processes frequently in favor of file system performance, resulting in large disk cache sizes. A value of 1 tells the kernel to only swap processes to disk if absolutely necessary. This can be set through a command like "echo 1 > /proc/sys/vm/swappiness"</li>
<li><b>numa_balancing</b>: Disabled through "echo 0 > /proc/sys/kernel/numa_balancing". This feature will automatically migrate data on demand so memory nodes are aligned to the local CPU that is accessing data. Depending on the workload involved, enabling this can boost the performance if the workload performs well on NUMA hardware. If the workload is statically set to balance between nodes, then this service may not provide a benefit.</li>
<li><b>Zone Reclaim Mode</b>: 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. To tell the kernel to free local node memory rather than grabbing free memory from remote nodes, use a command like "echo 1 > /proc/sys/vm/zone_reclaim_mode"</li>
</ul>

<p><b>tuned-adm</b>:</p>
<p>The tuned-adm is a tool allows selecting/applying different tuning profiles (such as throughput-performance, latency-performance, server-powersave, etc) supported in many Linux distributions. </p>
<ul>
<li>Use “tuned-adm list” to list all available profiles</li>
<li>Use “tuned-adm active” to list the currently configured profile</li>
<li>Use “tuned-adm profile "profile-name"” to apply or set a specific profile</li>
<li>throughput-performance: Server profile for typical throughput tuning. This profile disables tuned and ktune power saving features, enables sysctl settings that may improve disk and network IO throughput performance, switches to the deadline scheduler, and sets the CPU governor to performance.</li>
<li>balanced: Provides a balance between performance and power consumption. The profile uses auto-scaling and auto-tuning when possible. A possible drawback is increased latency.</li>
<li>latency-performance: Server profile for typical latency tuning. This profile disables tuned and ktune power saving features, enables the deadline IO scheduler, and sets the CPU governor to performance.</li>
<li>enterprise-storage: Server profile to high disk throughput tuning. This profile disables tuned and ktune power saving features, enables the deadline IO scheduler, enables hugepages and disables disk barriers, increases disk readahead values, and sets the CPU governor to performance</li>
<li>virtual-host: Server profile to optimized for KVM virtualization hosts. It decreases virtual memory swappiness, mounts non-root file systems to avoid metadata barriers, and enables aggressive writeback of dirty pages to disk.</li>
<li>Refer to the OS documentation for more details on the tuned profile.</li>
</ul>

<p><b>Transparent Huge Pages (THP)</b>:</p>
<p>Transparent Hugepages can be used to increase the memory page size from 4 kilobytes to 2 megabytes. THP provide significant performance advantages on systems with highly contended resources and large memory workloads. If memory utilization is too high or memory is badly fragmented which prevents hugepages being allocated, the kernel will assign smaller 4k pages instead.</p>
<ul>
<li><b> Examples </b></li>
<li> echo always >/sys/kernel/mm/transparent_hugepage/enabled </li> 
<li> echo madvise >/sys/kernel/mm/transparent_hugepage/enabled </li> 
<li> echo never >/sys/kernel/mm/transparent_hugepage/enabled </li> 
<li> Refer to the OS documentation for more details on THP.</li> 
</ul>


]]>
</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 Hyper-Threading (Default = Enabled):</b></p>
<p>This feature allows enabling or disabling of logical processor cores on processors supporting Intel Hyper-Threading (HT).  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>Intel Virtualization Technology (Intel VT, VT-x) (Default = Enabled):</b></p>
<p>When enabled, a hypervisor or operating system supporting this option can use hardware capabilities provided by Intel VT. Some hypervisors require that you enable Intel VT. You can leave this set to enabled even if you are not using a hypervisor or an operating system that uses this option. With default BIOS settings as shipped with most systems, the default state for this setting is Enabled. However, this setting can change it's default setting depending on the Workload Profile that is selected, or what Workload Profile is default for a certain system.</p>

<p><b>VT-d (Intel VT-d) (Default = Enabled):</b></p>
<p>If enabled, a hypervisor or operating system supporting this option can use hardware capabilities provided by Intel VT for Directed I/O. You can leave this set to enabled even if you are not using a hypervisor or an operating system that uses this option. With default BIOS settings as shipped with most systems, the default state for this setting is Enabled. However, this setting can change it's default setting depending on the Workload Profile that is selected, or what Workload Profile is default for a certain system.</p>

<p><b>Processor x2APIC Support (Default = Enabled):</b></p>
<p>If enabled, x2APIC support enables operating system to run more efficiently on high core count configurations. It also optimizes interrupt distribution in virtualized environments. Setting this option to Enabled is recommended for most cases. When enabled, the operating system can optionally enable x2APCI support when it loads. Older hypervisors and operating systems might have issues with optional x2APIC support, therefore disabling x2APIC could be necessary to address these issues. Setting this option to Enabled also forces Intel VT-D to be enabled.</p>

<p><b>SR-IOV (Default = Enabled):</b></p>
<p>If enabled, SR-IOV support enables a hypervisor to create virtual instances of PCI-express device, potentially increasing performance. If enabled, the BIOS allocates additional resources to PCI-express devices. You can leave this option set to Enabled even if you are not using a hypervisor. With default BIOS settings as shipped with most systems, the default state for this setting is Enabled. However, this setting can change it's default setting depending on the Workload Profile that is selected, or what Workload Profile is default for a certain system.</p>

<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-HPE 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 for this platform.</li>
</ul>


<p><b>Enhanced Processor Performance Profile (Default = Disabled):</b></p>
<p>Use this option to enable or disable processor performance profile. Based upon the selection, this feature will adjust the processor settings for improved performance, but may result in higher power consumption. Values for this BIOS option can be:</p>
<ul>
<li><b>Disabled</b>: No adjustments are made to the system for performance with no change in power consumption. </li>
<li><b>Enabled</b>: Enabling the option can provide improvement in performance, but may result in higher power consumption. </li>
</ul>

<p><b>Workload Profile (Default = General Power Efficient Compute):</b></p>
<p>This option allows a user to choose one workload profile that best fits the user`s needs. The workload profiles control many power and performance settings that are relevant to general workload areas. Values for this BIOS option can be:</p>
<ul>
<li>General Power Efficient Compute, General Peak Frequency Compute, General Throughput Compute, Virtualization - Power Efficient, Virtualization - Max Performance, Low Latency, Mission Critical, Transaction Application Processing, High Performance Compute (HPC), Decision Support, Graphic Processing, I/O Throughput, or Custom.</li>
<li>Setting the Workload Profile to any option not named Custom allows the server to automatically configure various BIOS settings. These BIOS settings control many power and performance settings that are relevant to general workload areas that fit the profile name.</li>
<li>Setting the Workload Profile to Custom allows a user to set any BIOS setting to any supported setting. Choosing Custom after selecting an initial profile does not change the settings controlled by the profile previously selected without user intervention.</li>
<li>Further technical description about what settings a Workload Profile changes and the types of workloads that a profile may be suitable for can be found through the HPE UEFI Workload-based Performance and Tuning Guide - https://support.hpe.com/hpesc/public/docDisplay?docId=sd00002647en_us&amp;page=GUID-E67BD113-8D65-4C61-B5AC-4A26F58FCCF3.html</li>
</ul>


<p><b>Power Regulator (Default = Static High Performance Mode):</b></p> 
<p>This option can only be configured if the Workload Profile is set to Custom. This feature allows the user to select the following Power Regulator support:</p>
<ul>
<li><b>Dynamic Power Savings Mode</b>: This mode allows the automatic variation of the processor speed and power usage based on processor utilization, resulting a reduction in overall power consumption with little or no impact on performance. It does not require OS support. </li>
<li><b>Static Low Power Mode</b>: This mode reduces the processor speed and power usage and guarantees a lower maximum power usage for the system.</li>
<li><b>Static High Performance Mode</b>: This mode allows the processors to run in their maximum power/performance state at all times, regardless of the OS power management policy.</li>
<li><b>OS Control Mode</b>: This mode allows the processors to 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 Workload Profile is set to Custom, or this option is not a dependent value for the Workload Profile. This feature selects the processor's lowest idle 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 for 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 is considered for 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 Workload Profile is set to Custom, or this option is not a dependent value for the Workload Profile. 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 lowest 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 Workload Profile is set to Custom, or this option is not a dependent value for the Workload Profile. 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</b>: Should be used for environments that require the highest performance and lowest latency but are not sensitive to power consumption.</li>
<li><b>Balanced Power</b>: Similar to Balanced Performance but this option prioritizes more power savings at the sacrifice of performance.</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>Energy Efficient Turbo (Default = Enabled):</b></p>
<p>This option controls whether the processor uses an energy efficiency based policy when engaging turbo range frequencies. This option is only applicable when Turbo Mode is enabled. Values for this BIOS setting can be: Enabled or Disabled.</p>

<p><b>HW Prefetcher (Default = Enabled):</b></p>
<p>Use this option to disable the processor HW Prefetch feature. In some cases, setting this option to disabled can improve performance. Typically, setting this option to enabled provides better performance. Only disable this option after performing application benchmarking to verify improved performance in the environment. The HW Prefetcher fetches streams of data and instruction from the memory into the second-level (L2) cache if it determines this data is likely to be required in the near future. The prefetcher is capable of handling multiple streams in either the forward or backward direction. The HW Prefetcher is triggered when successive cache misses occur in the last-level cache and a stride in the access pattern is detected, such as in the case of loop iterations that access array elements. The prefetching occurs up to a page boundary. This option can reduce the latency associated with memory reads. Values for this BIOS setting can be enabled or disabled.</p>

<p><b>Adjacent Sector Prefetch (Default = Enabled):</b></p>
<p>Use this option to disable the processor Adjacent Sector Prefetch feature. In some cases, setting this option to disabled can improve performance. Typically, setting this option to enabled provides better performance. Only disable this option after performing application benchmarking to verify improved performance in the environment. The Adjacent Sector Prefetch retrieves both sectors of a cache line when it requires data that isn't currently in the cache. When disabled, the processor will only fetch the sector of the cache line that includes the requested data. Values for this BIOS setting can be enabled or disabled.</p>

<p><b>Intel DMI Link Frequency (Default = Auto):</b></p>
<p>Use this option to set the DMI Link frequency to a lower frequency between the processor and PCH. Running at a lower frequency can reduce power consumption, but can also affect system performance. Values for this BIOS setting can be:</p>
<ul>
<li><b>Auto</b>: This option will enable the system to run with the highest supported DMI link speed.</li>
<li><b>Gen1 Speed</b>: This option will enable the system to run with Gen1 speed of 2.5 Gbps</li>
<li><b>Gen2 Speed</b>: This option will enable the system to run with Gen2 speed of 5.0 Gbps</li>
</ul>


<p><b>Last modified June 30, 2026.</b></p>
]]>
</firmware>

</flagsdescription>
