CPU2017 Flag Description
Fujitsu PRIMERGY RX2450 M1, AMD EPYC 7452, 2.35 GHz

Test sponsored by Fujitsu

Compilers: AMD Optimizing C/C++ Compiler Suite


Base Compiler Invocation

C benchmarks

C++ benchmarks

Fortran benchmarks


Base Portability Flags

500.perlbench_r

502.gcc_r

505.mcf_r

520.omnetpp_r

523.xalancbmk_r

525.x264_r

531.deepsjeng_r

541.leela_r

548.exchange2_r

557.xz_r


Base Optimization Flags

C benchmarks

C++ benchmarks

Fortran benchmarks


Implicitly Included Flags

This section contains descriptions of flags that were included implicitly by other flags, but which do not have a permanent home at SPEC.


Commands and Options Used to Submit Benchmark Runs

Using numactl to bind processes and memory to cores

For multi-copy runs or single copy runs on systems with multiple sockets, it is advantageous to bind a process to a particular core. Otherwise, the OS may arbitrarily move your process from one core to another. This can affect performance. To help, SPEC allows the use of a "submit" command where users can specify a utility to use to bind processes. We have found the utility 'numactl' to be the best choice.

numactl runs processes with a specific NUMA scheduling or memory placement policy. The policy is set for a command and inherited by all of its children. The numactl flag "--physcpubind" specifies which core(s) to bind the process. "-l" instructs numactl to keep a process's memory on the local node while "-m" specifies which node(s) to place a process's memory. For full details on using numactl, please refer to your Linux documentation, 'man numactl'

Note that some older versions of numactl incorrectly interpret application arguments as its own. For example, with the command "numactl --physcpubind=0 -l a.out -m a", numactl will interpret a.out's "-m" option as its own "-m" option. To work around this problem, we put the command to be run in a shell script and then run the shell script using numactl. For example: "echo 'a.out -m a' > run.sh ; numactl --physcpubind=0 bash run.sh"


Shell, Environment, and Other Software Settings

Transparent Huge Pages (THP)

THP is an abstraction layer that automates most aspects of creating, managing, and using huge pages. THP is designed to hide much of the complexity in using huge pages from system administrators and developers, as normal huge pages must be assigned at boot time, can be difficult to manage manually, and often require significant changes to code in order to be used effectively. Most recent Linux OS releases have THP enabled by default.

Linux Huge Page settings

If you need finer control you can manually set huge pages using the following steps:

Note that further information about huge pages may be found in the Linux kernel documentation file hugetlbpage.txt.

ulimit -s <n>

Sets the stack size to n kbytes, or unlimited to allow the stack size to grow without limit.

ulimit -l <n>

Sets the maximum size of memory that may be locked into physical memory.

powersave -f (on SuSE)

Makes the powersave daemon set the CPUs to the highest supported frequency.

/etc/init.d/cpuspeed stop (on Red Hat)

Disables the cpu frequency scaling program in order to set the CPUs to the highest supported frequency.

LD_LIBRARY_PATH

An environment variable that indicates the location in the filesystem of bundled libraries to use when running the benchmark binaries.

kernel/randomize_va_space

This option can be used to select the type of process address space randomization that is used in the system, for architectures that support this feature.

MALLOC_CONF

An environment variable set to tune the jemalloc allocation strategy during the execution of the binaries. This environment variable setting is not needed when building the binaries on the system under test.


Operating System Tuning Parameters

ulimit
This sets user limits of system-wide resources and can set the stack size to n kbytes, or unlimited to allow the stack size to grow without limit. Some common ulimit commands may include:
Kernel parameters
The following Linux Kernel parameters were set for better optimize performance.

Firmware / BIOS / Microcode Settings

ACPI _CST C1 Declaration
This BIOS switch allows 3 options: "Disabled", "Enabled", and "Auto". This feature determines whether or not to declare the C1 state to OS. Default is Auto.
cTDP
Configures the maximum power that the CPU will consume, up to the platform power limit. Valid values vary by CPU model. If value outside the valid range is set, the CPU will automatically adjust the value so that it does fall within the valid range. When increasing cTDP, additional power will only be consumed up to the Package Power Limit, which may be less than the cTDP setting.
ModelMinimum cTDPMaximum cTDP
EPYC 7502180200
EPYC 7452155180
EPYC 7402180200
EPYC 7352155180
EPYC 7302155180
EPYC 7282120150
EPYC 7262155180
EPYC 7252120150
Determinism Slider
This BIOS switch allows 3 options: "Auto", "Power", and "Performance". This feature is for the determinism to control performance. "Auto" setting uses default values for deterministic performance control. "Power" setting provides predicable performance across all processors of the same type. "Power" setting maximizes performance withing the power limits defined by cTDP. Default is "Auto".
DRAM Scrub Time
This feature controls the time between DRAM Scrubbing, which cyclically accesses the main memory of the system in the background regardless of the operating system in order to detect and correct memory errors in a preventive way. This BIOS switch allows 8 options: "Disabled", "1 hour", "4 hours", "8 hours", "16 hours", "24 hours", "48 hours", and "Auto". "Disabled" option disables the feature of DRAM Scrubbing and it may result in improving the performance under certain circumstances but increases the probability of discovering memory errors in case of active accesses by the operating system. Until these errors are correctable, the ECC technology of the memory modules ensures that the system continues to run in a stable way. However, too many correctable memory errors increase the risk of discovering non-correctable errors, which then result in a system standstill.
Global C-state Control
This BIOS switch allows 2 options: "Disabled", "Enabled, and "Auto". This feature controls IO based C-state generation and DF C-states. Default is "Auto"
L1 Stream HW Prefetcher
This BIOS switch allows 2 options: "Disabled", "Enabled, and "Auto". This feature allows enabling or disabling of L1 Stream HW Prefetcher. Auto. Default is "Auto".
L2 Stream HW Prefetcher
This BIOS switch allows 2 options: "Disabled", "Enabled, and "Auto". This feature allows enabling or disabling of L2 Stream HW Prefetcher. Default is "Auto".
NUMA nodes per socket
This BIOS switch allows 5 options: "NPS0", "NPS1", "NPS2", "NPS4", and "Auto". This feature specifies the number of desired NUMA nodes per populated socket in the system: Default is "Auto" (PRIMERGY RX servers) or "NPS4" (PRIMERGY GX servers).
Package Power Limit
This BIOS switch specifies the maximum power that each CPU package may consume in the system. The actual power limit is the maximum of the Package Power Limit and cTDP.
SMT Control
This BIOS switch allows 2 options: "Auto" and "Disabled". This feature allows enabling or disabling of symmetric multithreading on processors. When enabled, each physical processor core operates as two logical processor cores. When disabled, each physical core operates as only one logical processor core. "Auto" enables this feature and can improve overall performance for applications that benefit from a higher processor core count. Default is "Auto" (PRIMERGY RX servers) or "Disabled" (PRIMERGY GX servers).
SVM Mode
This BIOS switch allows 2 options: "Enabled" and "Disabled". This is CPU virtualization function. With SVM enabled virtual machines can be installed on the system. Default is "Disabled" (PRIMERGY RX servers) or "Enabled" (PRIMERGY GX servers).

Flag description origin markings:

[user] Indicates that the flag description came from the user flags file.
[suite] Indicates that the flag description came from the suite-wide flags file.
[benchmark] Indicates that the flag description came from a per-benchmark flags file.

The flags files that were used to format this result can be browsed at
http://www.spec.org/cpu2017/flags/aocc200-flags-C4.html,
http://www.spec.org/cpu2017/flags/Fujitsu-Platform-Settings-V1.0-ROME-RevE.html.

You can also download the XML flags sources by saving the following links:
http://www.spec.org/cpu2017/flags/aocc200-flags-C4.xml,
http://www.spec.org/cpu2017/flags/Fujitsu-Platform-Settings-V1.0-ROME-RevE.xml.


For questions about the meanings of these flags, please contact the tester.
For other inquiries, please contact info@spec.org
Copyright 2017-2021 Standard Performance Evaluation Corporation
Tested with SPEC CPU2017 v1.1.5.
Report generated on 2021-04-27 16:20:17 by SPEC CPU2017 flags formatter v5178.