<?xml version="1.0"?>

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

<flagsdescription>

<filename>Quanta-Computer-Inc-Birch_Stream-Platform-Settings-V1.4</filename>

<title>SPEC CPU2017 software OS and BIOS Settings Descriptions for Quanta Computer Inc. Platform 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 Performance governor and Powersave governor:</p>
<p><b>--governor , -g</b></p>
<p>The governor defines the power characteristics of the system CPU, which in turn affects CPU performance. Each governor has its own unique behavior, purpose, and suitability in terms of workload.</p>
<p>On many Linux systems one can set the governor for all CPUs through the cpupower utility with following commands:</p>
<ul>
<li>"cpupower frequency-set -g performance"</li>
</ul>

<p><b>tuned-adm</b>:</p>
<p>The tuned-adm tool is a commandline interface for switching between different tuning profiles available to the tuned tuning daeomn available in supported Linux distros. The default configuration file is located in /etc/tuned.conf and the supported profiles can be found in /etc/tune-profiles.</p>
<p>Some profiles that may be available by default include: default, desktop-powersave, server-powersave, laptop-ac-powersave, laptop-battery-powersave, spindown-disk, throughput-performance, latency-performance, enterprise-storage</p>
<p>To set a profile, one can issue the command "tuned-adm profile (profile_name)". Here are details about relevant profiles. </p>
<ul>
<li><b>throughput-performance</b>: 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 throughphut performance, switches to the deadline scheduler, and sets the CPU governor to performance.</li>
<li><b>latency-performance</b>: 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><b>enterprise-storage</b>: 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>
</ul>

<p><b>Transparent Hugepages (THP)</b></p>
<p>THP is an abstraction layer that automates most aspects of creating, managing,and using huge pages. It is designed to hide much of the complexity in using huge pages from system administrators and developers.  Huge pages increase the memory page size from 4 kilobytes to 2 megabytes. This provides 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. Most recent Linux OS releases have THP enabled by default.</p>
<p>THP usage is controlled by the sysfs setting <tt>/sys/kernel/mm/transparent_hugepage/enabled</tt>.</p>
<p>Possible values:</p>
    <ul>
      <li>never: entirely disable THP usage.</li>
      <li>madvise: enable THP usage only inside regions marked MADV_HUGEPAGE using madvise(3).</li>
      <li>always: enable THP usage system-wide. This is the default.</li>
    </ul>
<p>THP creation is controlled by the sysfs setting <tt>/sys/kernel/mm/transparent_hugepage/defrag</tt>.</p>
<p>Possible values:</p>
    <ul>
      <li>never: if no THP are available to satisfy a request, do not attempt to make any.</li>
      <li>defer: an allocation requesting THP when none are available get normal pages while requesting THP creation in the background.</li>
      <li>defer+madvise: acts like "always", but only for allocations in regions marked MADV_HUGEPAGE using madvise(3); for all other regions it's like "defer".</li>
      <li>madvise: acts like "always", but only for allocations in regions marked MADV_HUGEPAGE using madvise(3).  This is the default.</li>
      <li>always: an allocation requesting THP when none are available will stall until some are made.</li>
    </ul>
<p>An application that "always" requests THP often can benefit from waiting for an allocation until those huge pages can be assembled.</p>
<p>For more information see the <a href="https://www.kernel.org/doc/Documentation/vm/transhuge.txt">Linux transparent hugepage documentation</a>.</p>

]]>
</os_tuning>

<firmware>
<![CDATA[
<p><b>Enable LP [Global] (Default = ALL LPs):</b></p>
<p>Enables Logical processor (Software Method to Enable/Disable Logical Processor threads)</p>
<ul>
<li><b>ALL LPs</b></li>
<li><b>Single LP</b></li>
</ul>

<p><b>SNC (Sub NUMA) (Default = AUTO):</b></p>
<p> Disable supports 1-cluster and 4-IMC way interleave. Enable SNC2 supports 2-clusters SNC and 2-way IMC interleave. Auto - Auto decides based on Si Compatibility.</p>
<ul>
<li><b>AUTO</b></li>
<li><b>Disable</b></li>
<li><b>Enable</b></li>
</ul>

<p><b>LLC dead line alloc (Default = Enable):</b></p>
<p>Enable - opportunistically fill dead lines in LLC. Disable - never fill dead lines in LLC, Auto - Auto decides based on Si Compatibility.</p>
<ul>
<li><b>Disable</b>: Disabling this option can save space in the LLC by never filling dead lines into the LLC. This can and prevent useful data from being evicted.</li>
<li><b>Enable</b>: Opportunistically fill dead lines in LLC, if space is available.</li>
<li><b>Auto</b></li>
</ul>

<p><b>Patrol Scrub (Default = Enable at End of POST):</b></p>
<p>This option allows for correction of soft memory errors. Over the length of system runtime, the risk of producing multi-bit and uncorrected errors is reduced with this option. Values for this BIOS setting can be:</p>
<ul>
<li><b>Disabled</b>: Soft memory error correction is turned off during runtime.</li>
<li><b>Enable at End of POST</b>: Correction of soft memory errors can occur during runtime.</li>
</ul>

<p><b>Xtended Prediciton Table (XPT) Prefetch (Default = Auto):</b></p>
<p>This option configures the processor Xtended Prediciton Table (XPT) prefetch feature. The XPT prefetcher exists on top of other prefetchers that that can prefetch data in the core DCU, MLC, and LLC. The XPT prefetcher will issue a speculative DRAM read request in parallel to an LLC lookup.  This prefetch bypasses the LLC, saving latency.  In some cases, setting this option to disabled can improve performance. Typically, setting this option to enable provides better performance. This option must be enabled when Sub-NUMA Clustering is enabled. Values for this BIOS option can be:</p>
<ul>
<li><b>Enable</b>: Allows a read request sent to the LLC to speculatively issue a copy of the read to the memory controller requesting the prefetch.</li>
<li><b>Disable</b>: Does not allow the LLC to speculatively issue copies of reads. Disabling this will also disables Sub-NUMA Cluster (SNC).</li>
<li><b>Auto</b></li>
</ul>

<p><b>DCU Streamer Prefetcher (Default = Auto):</b></p>
<p>This prefetcher is a L1 data cache prefetcher, which detects multiple loads from the same cache line done within a time limit, in order to then prefetch the next line from the L2 cache or the main memory into the L1 cache based on the assumption that the next cache line will also be needed.</p>
<ul>
<li><b>Disable</b></li>
<li><b>Enable</b></li>
<li><b>Auto</b></li>
</ul>

<p><b>LLC Prefetch (Default = Disable):</b></p>
<p>Enable/Disable LLC Prefetch on all threads.</p>
<ul>
<li><b>Enable</b></li>
<li><b>Disable</b></li>
</ul>

<p><b>Package C State (Default = Auto):</b></p>
<p>Package C-states is one of energy-saving options of the processor, which not only allow the individual cores of a processor, but the entire processor chip to be put into a type of sleep state. As a result, power consumption is even further reduced. But the "waking-up time" that is required to change from the lower package C-states to the active (C0) state is even longer in comparison with the CPU or core C-states.</p>
<ul>
<li><b>C0/C1 state</b>:The processor chip always remains active. It can improve the performance of latency sensitive workloads</li>
<li><b>C2 state</b>:System reduces power consumption more than with the C0/C1 option and slightly longer wake-up time to high-performance mode.</li>
<li><b>C6(non Retention) state</b>:This option saves more power but longer wake-up time to high-performance mode.</li>
<li><b>No Limit</b>:No restrictions on entering any C-state.</li>
<li><b>Auto</b>: Automatically manages Package C-states based on workload.</li>
</ul>

<p><b>Energy/Performance Bias (Default = Balanced Performance):</b></p>
<p>Use input from ENERGY_PERF_BIAS_CONFIG mode selection. PERF/Balanced Perf/Balanced Power/Power</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>Intel  VT for Directed I/O (Default = Enable):</b></p>
<p>Enable/Disable Intel  Virtualization Technology for Directed I/O (VT-d) by reporting the I/O device assignment to VMM through DMAR ACPI Tables.</p>
<ul>
<li><b>Enable</b></li>
<li><b>Disable</b></li>
</ul>

<p><b>Virtual Numa (Default = Disable):</b></p>
<p>Divide physical NUMA nodes into evenly sized virtual NUMA nodes in ACPI table. This may improve Windows performance on CPUs with more than 64 logical processors.</p>
<ul>
<li><b>Enable</b></li>
<li><b>Disable</b></li>
</ul>

<p><b>Hardware P-States (Default = Native Mode):</b></p>
<p>The Hardware P-State setting allows the user to select between OS and hardware-controlled P-states.</p>
<ul>
<li><b>Disable</b>: Hardware chooses a P-state based on OS Request (Legacy P-States)</li>
<li><b>Native Mode</b>:Hardware chooses a P-state based on OS guidance</li>
<li><b>Out Of Band Mode</b>:Hardware autonomously chooses a P-state (no OS guidance)</li>
<li><b>Native Mode With No Legacy Support</b>:Hardware chooses a P-state based on OS guidance with no support for older hardware</li>
</ul>

<p><b>Last updated August 7, 2024.</b></p>
]]>
</firmware>

</flagsdescription>
