CPU2017 Flag Description
Fujitsu PRIMERGY TX1330 M4, Intel Xeon E-2126G, 3.30GHz

Copyright © 2016 Intel Corporation. All Rights Reserved.


Base Compiler Invocation

C benchmarks

C++ benchmarks

Fortran benchmarks

Benchmarks using both Fortran and C

Benchmarks using both C and C++

Benchmarks using Fortran, C, and C++


Peak Compiler Invocation

C benchmarks

C++ benchmarks

Fortran benchmarks

Benchmarks using both Fortran and C

Benchmarks using both C and C++

Benchmarks using Fortran, C, and C++


Base Portability Flags

503.bwaves_r

507.cactuBSSN_r

508.namd_r

510.parest_r

511.povray_r

519.lbm_r

521.wrf_r

526.blender_r

527.cam4_r

538.imagick_r

544.nab_r

549.fotonik3d_r

554.roms_r


Peak Portability Flags

503.bwaves_r

507.cactuBSSN_r

508.namd_r

510.parest_r

511.povray_r

519.lbm_r

521.wrf_r

526.blender_r

527.cam4_r

538.imagick_r

544.nab_r

549.fotonik3d_r

554.roms_r


Base Optimization Flags

C benchmarks

C++ benchmarks

Fortran benchmarks

Benchmarks using both Fortran and C

Benchmarks using both C and C++

Benchmarks using Fortran, C, and C++


Peak Optimization Flags

C benchmarks

519.lbm_r

538.imagick_r

544.nab_r

C++ benchmarks

Fortran benchmarks

503.bwaves_r

549.fotonik3d_r

554.roms_r

Benchmarks using both Fortran and C

Benchmarks using both C and C++

511.povray_r

526.blender_r

Benchmarks using Fortran, C, and C++

507.cactuBSSN_r


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

submit= MYMASK=`printf '0x%x' $((1<<$SPECCOPYNUM))`; /usr/bin/taskset $MYMASK $command
When running multiple copies of benchmarks, the SPEC config file feature submit is used to cause individual jobs to be bound to specific processors. This specific submit command, using taskset, is used for Linux64 systems without numactl.
Here is a brief guide to understanding the specific command which will be found in the config file:
submit= numactl --localalloc --physcpubind=$SPECCOPYNUM $command
When running multiple copies of benchmarks, the SPEC config file feature submit is used to cause individual jobs to be bound to specific processors. This specific submit command is used for Linux64 systems with support for numactl.
Here is a brief guide to understanding the specific command which will be found in the config file:

Shell, Environment, and Other Software Settings

numactl --interleave=all "runspec command"
Launching a process with numactl --interleave=all sets the memory interleave policy so that memory will be allocated using round robin on nodes. When memory cannot be allocated on the current interleave target fall back to other nodes.
KMP_STACKSIZE
Specify stack size to be allocated for each thread.
KMP_AFFINITY
Syntax: KMP_AFFINITY=[<modifier>,...]<type>[,<permute>][,<offset>]
The value for the environment variable KMP_AFFINITY affects how the threads from an auto-parallelized program are scheduled across processors.
It applies to binaries built with -qopenmp and -parallel (Linux and Mac OS X) or /Qopenmp and /Qparallel (Windows).
modifier:
    granularity=fine Causes each OpenMP thread to be bound to a single thread context.
type:
    compact Specifying compact assigns the OpenMP thread <n>+1 to a free thread context as close as possible to the thread context where the <n> OpenMP thread was placed.
    scatter Specifying scatter distributes the threads as evenly as possible across the entire system.
permute: The permute specifier is an integer value controls which levels are most significant when sorting the machine topology map. A value for permute forces the mappings to make the specified number of most significant levels of the sort the least significant, and it inverts the order of significance.
offset: The offset specifier indicates the starting position for thread assignment.

Please see the Thread Affinity Interface article in the Intel Composer XE Documentation for more details.

Example: KMP_AFFINITY=granularity=fine,scatter
Specifying granularity=fine selects the finest granularity level and causes each OpenMP or auto-par thread to be bound to a single thread context.
This ensures that there is only one thread per core on cores supporting HyperThreading Technology
Specifying scatter distributes the threads as evenly as possible across the entire system.
Hence a combination of these two options, will spread the threads evenly across sockets, with one thread per physical core.

Example: KMP_AFFINITY=compact,1,0
Specifying compact will assign the n+1 thread to a free thread context as close as possible to thread n.
A default granularity=core is implied if no granularity is explicitly specified.
Specifying 1,0 sets permute and offset values of the thread assignment.
With a permute value of 1, thread n+1 is assigned to a consecutive core. With an offset of 0, the process's first thread 0 will be assigned to thread 0.
The same behavior is exhibited in a multisocket system.
OMP_NUM_THREADS
Sets the maximum number of threads to use for OpenMP* parallel regions if no other value is specified in the application. This environment variable applies to both -qopenmp and -parallel (Linux and Mac OS X) or /Qopenmp and /Qparallel (Windows). Example syntax on a Linux system with 8 cores: export OMP_NUM_THREADS=8
Set stack size to unlimited
The command "ulimit -s unlimited" is used to set the stack size limit to unlimited.
Free the file system page cache
The command "echo 1> /proc/sys/vm/drop_caches" is used to free up the filesystem page cache.

Red Hat Specific features

Transparent Huge Pages
On RedHat EL 6 and later, Transparent Hugepages increase the memory page size from 4 kilobytes to 2 megabytes. Transparent Hugepages 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.
Hugepages are used by default unless the /sys/kernel/mm/redhat_transparent_hugepage/enabled field is changed from its RedHat EL6 default of 'always'.

Operating System Tuning Parameters

sched_cfs_bandwidth_slice_us
When Completely Fair Scheduler bandwidth control is in use, this parameter controls the amount of run-time (bandwidth) transferred to a run queue from the task's control group bandwidth pool. Small values allow the global bandwidth to be shared in a fine-grained manner among tasks, larger values reduce transfer overhead.
The default value is 5000

Firmware / BIOS / Microcode Settings

Adjacent Cache Line Prefetch
This BIOS option allows 2 options: "Enabled" and "Disabled".
This prefetcher always collects cache line pairs (128 bytes) from the main memory, providing that the data is not already contained in the cache. If this prefetcher is disabled, only one cache line (64 bytes) is collected, which contains the data required by the processor.
Default setting is "Enabled".
DMI Link ASPM Control
This BIOS option allows 4 options: "Disabled", "L0s", "L1" and "L0sL1".
The control of Active State Power Management(ASPM) supported on the Direct Media Interface(DMI) Link. L0s: L0s entry supported. L1: L1 entry supported. L0sL1: L0s and L1 entry supported. Disabled: No ASPM entry supported.
Default setting is "L1".
Energy Efficient Turbo
This BIOS option allows 2 options: "Enabled" and "Disabled".
This feature will opportunistically lower the turbo frequency to increase energy efficiency. If this option is disabled, turbo frequency will remain constant.
Default setting is "Auto".
Fan Control
This BIOS option allows 2 options: "Auto" and "Full".
The default setting is "Auto", which allows the system to control the fan speed according to the system temperature. If "Full" is selected, the system runs fans at 100% speed and it may improve the system performance. But it increases the power consumption of the system.
Default setting is "Auto".
Hardware Prefetcher
This BIOS option allows 2 options: "Enabled" and "Disabled".
This prefetcher looks for data streams on the assumption that if the data is requested at address A and A+1, the data will also presumably be required at address A+2. This data is then prefetched into the L2 cache from the main memory.
Default setting is "Enabled".
Hyper-Threading
This BIOS option enables or disables additional hardware thread which shares same physical core. Generally "Enabled" is recommended but disabling it makes sense for the application which requires the shortest possible response times.
Default setting is "Enabled".
Native PCIE Enable
This BIOS option allows 2 options: "Enabled" and "Disabled".
This feature enables or disables OS to control below features: Hot Plug, SHPC Native Hot Plug control, Power Management Events, PCIe Advanced Error Reporting control, PCIe Capability Structure control, and Latency Tolerance Reporting control.
Default setting is "Enabled".
Package C-State Un-demotion
This BIOS option allows 2 options: "Enabled" and "Disabled".
This feature enables processor to switch back to the original requested deeper Package C-state considering cases where demotion was the incorrect decision in determing Package C-state depth.
Default setting is "Disabled".
Race To Halt (RTH)
This BIOS option allows 2 options: "Enabled" and "Disabled".
RTH will dynamically increase CPU frequency in order to enter Package C-State faster to reduce overall power.
Default setting is "Enabled".
REFRESH_2X_MODE
This BIOS option allows 3 options: "Disabled", "1- Enabled for WARM or HOT", and "2- Enabled HOT only".
This feature enables REFRESH 2X mode which maintains an acceptable overall error rate by increase DRAM refresh rate when temperature is WARM or HOT. 0 - Disabled. 1 - iMC enables 2xRefresh rate mode when thermal status is Warm or Hot. 2 - iMC enables 2xRefresh rate mode when thermal status is Hot
Default setting is "Disabled".
Software Guard Extensions (SGX)
This BIOS option allows 3 options: "Disabled", "Enabled", and "Software Controlled".
Intel(R) SGX is a CPU extension that applications can use to create and access private memory areas. When "Disabled" is selected, SGX is disabled and cannot be used by applications. When "Enabled" is selected, SGX is enabled and can be used by applications. The reserved size of the private memory is specified by the BIOS. When "Software Controlled" is selected, SGX is enabled and can be used by applications. The reserved size of the private memory is specified by the operating system (OS).
Default setting is "Software Controlled".
VT-d
This BIOS option enables or disables I/O virtualization functions of the CPU. If the server is not used for virtualization, this option should be set to "Disabled".
Default setting is "Enabled".

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/Intel-ic18.0-official-linux64.2017-12-21.html,
http://www.spec.org/cpu2017/flags/Fujitsu-Platform-Settings-V1.0.2-CFL-RevA.html.

You can also download the XML flags sources by saving the following links:
http://www.spec.org/cpu2017/flags/Intel-ic18.0-official-linux64.2017-12-21.xml,
http://www.spec.org/cpu2017/flags/Fujitsu-Platform-Settings-V1.0.2-CFL-RevA.xml.


For questions about the meanings of these flags, please contact the tester.
For other inquiries, please contact info@spec.org
Copyright 2017-2018 Standard Performance Evaluation Corporation
Tested with SPEC CPU2017 v1.0.2.
Report generated on 2018-11-13 15:17:43 by SPEC CPU2017 flags formatter v5178.