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.

Power Regulator for ProLiant support (Default=HP Dynamic Power Savings Mode)

Values for this BIOS setting can be:

• HP Dynamic Power Savings Mode: 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.
• HP Static Low Power Mode: 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.
• HP Static High Performance Mode: Processors will run in their maximum power/performance state at all times regardless of the OS power managment policy.
• OS Control Mode: Processors will run in their maximum power/ performance state at all times unless the OS enables' a power management policy.

HP Power Profile (Default = Balanced Power and Performance):

Values for this BIOS setting can be:

• Balanced Power and Performance: Provides the optimum settings to maximize power savings with minimal impact to performance for most Operating Systems and applications.
• Maximum Performance: Disables all power management options that may negatively affect performance.
• Minimum Power Usage: Enables power reduction mechanisms that may negatively affect performance. This mode will guarantee a lower maximum power usage by the system. - Maximum Performance: Disables all power management options that ma negatively affec performance.

Power Efficiency Mode (Default=Efficiency)

Values for this BIOS setting can be:

• Efficiency: Maximize the power efficiency of the server.
• Performance: Maximize the performance of the server.
• Custom: Allows the user to customize power and performance related options individually.

Adjacent Sector Prefetch (Default = Enabled):

This BIOS option allows the enabling/disabling of a processor mechanism to fetch the adjacent cache line within an 128-byte sector that contains the data needed due to a cache line miss.

In some limited cases, setting this option to Disabled may improve performance. In the majority of cases, the default value of Enabled provides better performance. Users should only disable this option after performing application benchmarking to verify improved performance in their environment.

Hardware Prefetch (Default = Enabled):

This BIOS option allows allows the enabling/disabling of a processor mechanism to prefetch data into the cache according to a pattern recognition algorithm.

In some limited cases, setting this option to Disabled may improve performance. In the majority of cases, the default value of Enabled provides better performance. Users should only disable this option after performing application benchmarking to verify improved performance in their environment.

Data Reuse (Default = Enabled):

This BIOS option allows allows the enabling/disabling of the Data Reuse optimization.

Enabling this option reduces the frequency of L3 cache updates from the L1 cache. This may improve performance by reducing the internal bandwidth consumed by constantly updating L1 cache lines in the L3 cache.

Since this optimization results in more fetches to main memory, in some limited cases, setting this option to Disabled may improve performance. In the majority of cases, the default value of Enabled provides better performance. Users should only disable this option after performing application benchmarking to verify improved performance in their environment.

Turbo Mode (Default = Enabled):

Turbo Boost Technology is a processor feature which allows the processor to transition to a higher frequency than the processor's rate speed if the processor has available power headroom and is within tempereature specifications. Disabling this feature will reduce power usage but will reduce the system's maximum achievable performance under some workloads.

Thermal Configuration (Default = Optimal Cooling):

This feature allows the user to select the fan cooling solution for the system. Values for this BIOS option can be:

• Optimal Cooling: Provides the most efficient solution by configuring fan speeds to the minimum required to provide adequate cooling.
• Increased Cooling: Will run fans at higher speeds to provide aditional 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. This option may also improve performance when Turbo Boost Technology is used.

Defer All Transactions Mode (Default = Disabled):

When this option is enabled, front-side bus bandwidth may be increased on systems with heavy I/O workload because CPU initiated I/O transactions can be deferred enabling other transactions to make progress while data is retrieved. However, latency for completing transactions may also increase. The system's workload will determine which setting will provide highest performance.

Memory Speed with 2DPC (Default=1066MHz@1.35V)

Sets the memory speed and voltage setting for system when there are 2 DIMMs per channel (2DPC). Values for this BIOS setting can be:

• 1333MHz@1.5V
• 1066MHz@1.35V

SATA #1 Controller (Default=Auto)

Sets the mode for the embedded controller. The values for this BIOS setting can be:

• Disabled: Disables SATA controller
• Compatible: Sets controller to IDE Compatiblity mode
• RAID: Sets controller to RAID mode
• AHCI: Sets controller to Advanced Host Controller Interface mode

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 sometimes used to cause individual jobs to be bound to specific processors. This specific submit command is used for Linux. The description of the elements of the command are:

• /usr/bin/taskset [options] [mask] [pid | command [arg] ... ]:
  taskset is used to set or retreive the CPU affinity of a running process given its PID or to launch a new COMMAND with a given CPU affinity. The CPU affinity is represented as a bitmask, with the lowest order bit corresponding to the first logical CPU and highest order bit corresponding to the last logical CPU. When the taskset returns, it is guaranteed that the given program has been scheduled to a legal CPU.
  
  The default behaviour of taskset is to run a new command with a given affinity mask:
  
  taskset [mask] [command] [arguments]
• $MYMASK: The bitmask (in hexadecimal) corresponding to a specific SPECCOPYNUM. For example, $MYMASK value for the first copy of a rate run will be 0x00000001, for the second copy of the rate will be 0x00000002 etc. Thus, the first copy of the rate run will have a CPU affinity of CPU0, the second copy will have the affinity CPU1 etc.
• $command: Program to be started, in this case, the benchmark instance to be started.

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 effect 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 memory on the local node while "-m" specifies which node(s) to place a process memory. For full details on using numactl, please refer to your Linux documentation, 'man numactl'

mysubmit.pl

This perl script is used to ensure that for a system with N cores the first N/2 benchmark copies are bound to a core that does not share its L2 cache with any of the other copies. The script does this by retrieving and using CPU data from /proc/cpuinfo. Note this script will only work for 6-core CPUs.

• Source
  ******************************************************************************************************
  #!/usr/bin/perl
  
  use strict;
  use Cwd;
  
  # The order in which we want copies to be bound to cores
  # Copies: 0, 1, 2, 3
  # Cores: 0, 1, 3, 6
  
  my $rundir = getcwd;
  
  my $copynum = shift @ARGV;
  
  my $i;
  my $j;
  my $tag;
  my $num;
  my $core;
  
  my @proc;
  my @cores;
  
  open(INPUT, "/proc/cpuinfo") or
  die "can't open /proc/cpuinfo\n";
  
  #open(OUTPUT, "STDOUT");
  
  # proc[i][0] = logical processor ID
  # proc[i][1] = physical processor ID
  # proc[i][2] = core ID
  
  $i = 0;
  
  while(<INPUT>)
  {
  chop;
  
  ($tag, $num) = split(/\s+:\s+/, $_);
  
  
  if ($tag eq "processor") {
  $proc[$i][0] = $num;
  }
  
  if ($tag eq "physical id") {
  $proc[$i][1] = $num;
  }
  
  if ($tag eq "core id") {
  $proc[$i][2] = $num;
  $i++;
  }
  }
  
  $i = 0;
  $j = 0;
  
  for $core (0, 4, 2, 1, 5, 3) {
  while ($i < 24) {
  if ($proc[$i][2] == $core) {
  $cores[$j] = $proc[$i][0];
  $j++;
  }
  $i++;
  }
  $i=0;
  }
  
  open RUNCOMMAND, "> runcommand" or die "failed to create run file";
  print RUNCOMMAND "cd $rundir\n";
  print RUNCOMMAND "@ARGV\n";
  close RUNCOMMAND;
  system 'taskset', '-c', $cores[$copynum], 'sh', "$rundir/runcommand";
  

ulimit -s [n | unlimited] (Linux)

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

KMP_STACKSIZE=integer[B|K|M|G|T] (Linux)

Sets the number of bytes to allocate for each parallel thread to use as its private stack. Use the optional suffix B, K, M, G, or T, to specify bytes, kilobytes, megabytes, gigabytes, or terabytes. The default setting is 2M on IA32 and 4M on IA64.

KMP_AFFINITY=physical,n (Linux)

Assigns threads to consecutive physical processors (for example, cores), beginning at processor n. Specifies the static mapping of user threads to physical cores, beginning at processor n. For example, if a system is configured with 8 cores, and OMP_NUM_THREADS=8 and KMP_AFFINITY=physical,2 are set, then thread 0 will mapped to core 2, thread 1 will be mapped to core 3, and so on in a round-robin fashion.

OMP_NUM_THREADS=n

This Environment Variable sets the maximum number of threads to use for OpenMP* parallel regions to n if no other value is specified in the application. This environment variable applies to both -openmp and -parallel (Linux) or /Qopenmp and /Qparallel (Windows). Example syntax on a Linux system with 8 cores:
export OMP_NUM_THREADS=8
Default is the number of cores visible to the OS.

vm.max_map_count-n (Linux)

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.