WHITE PAPER FUJITSU PRIMERGY SERVERS PERFORMANCE REPORT PRIMERGY RX100 S7P

Transcription

1 WHITE PAPER PERFORMANCE REPORT PRIMERGY RX100 S7P WHITE PAPER FUJITSU PRIMERGY SERVERS PERFORMANCE REPORT PRIMERGY RX100 S7P This document contains a summary of the benchmarks executed for the PRIMERGY RX100 S7p. The PRIMERGY RX100 S7p performance data are compared with the data of other PRIMERGY models and discussed. In addition to the benchmark results, an explanation has been included for each benchmark and for the benchmark environment. Version Fujitsu Technology Solutions 2012 Page 1 (24)

2 Contents Document history... 2 Technical data... 3 SPECcpu SPECjbb SPECpower_ssj OLTP STREAM LINPACK Literature Contact Document history Version 1.0 New: Technical data SPECcpu2006 Measurements with Celeron G500 processor series, Pentium G640 and Xeon E processor series SPECjbb2005 Measurement with Xeon E3-1280V2 SPECpower_ssj2008 Measurement with Xeon E3-1265LV2 and 1 SSD SATA 3G 32GB SLC HOT PLUG 2.5" EP OLTP-2 Results for Celeron G500 processor series, Pentium G640 and Xeon E processor series STREAM Measurements with Celeron G500 processor series, Pentium G640 and Xeon E processor series LINPACK Measurements with Celeron G500 processor series, Pentium G640 and Xeon E processor series Version 1.1 Updated: Technical data SPECcpu2006 Measurements with Core i OLTP-2 Results for Core i STREAM Measurement with Core i LINPACK Measurement with Core i Page 2 (24) Fujitsu Technology Solutions 2012

3 Technical data PRIMERGY RX100 S7p with 2.5" HDDs Decimal prefixes according to the SI standard are used for measurement units in this white paper (e.g. 1 GB = 10 9 bytes). In contrast, these prefixes should be interpreted as binary prefixes (e.g. 1 GB = 2 30 bytes) for the capacities of caches and storage modules. Separate reference will be made to any further exceptions where applicable. Model Model versions Form factor Chipset Number of sockets 1 type Number of memory slots 4 Maximum memory configuration Onboard LAN controller Onboard HDD controller PCI slots Max. number of internal hard disks PRIMERGY RX100 S7p PY RX100S7p/LFF/Standard PSU: 2-port SAS backplane for 2 hot plug LFF (3.5") SAS/SATA HDDs incl. cables for connection to the onboard SATA or plug-in SAS controller Standard-PSU PY RX100S7p/LFF/Hot-Plug PSU: 2-port SAS backplane for 2 hot plug LFF (3.5") SAS/SATA HDDs incl. cables for connection to the onboard SATA or plug-in SAS controller Hot-plug PSU PY RX100S7p/SFF/Standard PSU: 4-port SAS backplane for 4 hot plug SFF (2.5") SAS/SATA HDDs incl. cables for connection to the onboard SATA or plug-in SAS controller Standard-PSU PY RX100S7p/SFF/Hot-Plug PSU: 4-port SAS backplane for 4 hot plug SFF (2.5") SAS/SATA HDDs incl. cables for connection to the onboard SATA or plug-in SAS controller Hot-plug PSU Rack server Intel C200 series Intel Celeron series G500 Intel Pentium series G600 Intel Xeon series E GB 2 1 Gbit/s PY RX100S7p/LFF/Standard PSU and PY RX100S7p/LFF/Hot-Plug PSU: Controller with RAID 0 or RAID 1 for up to SATA HDDs PY RX100S7p/SFF/Standard PSU and PY RX100S7p/SFF/Hot-Plug PSU: Controller with RAID 0, RAID 1 or RAID 10 for up to SATA HDDs 1 PCI-Express 3.0 x16 1 PCI-Express 2.0 x1 (mech. x4) 1 PCI-Express 2.0 x4 (mech. x8) reserved for RAID card PY RX100S7p/LFF/Standard PSU and PY RX100S7p/LFF/Hot-Plug PSU: 2 PY RX100S7p/SFF/Standard PSU and PY RX100S7p/SFF/Hot-Plug PSU: 4 Fujitsu Technology Solutions 2012 Page 3 (24)

4 Capacity [GB] Ranks Bit width of the memory chips Frequency [MHz] Low voltage Load reduced Registered ECC Cores Threads WHITE PAPER PERFORMANCE REPORT PRIMERGY RX100 S7P VERSION: s (since system release) Cache [MB] Frequency [Ghz] Max. Turbo Frequency at full load [Ghz] Max. Turbo Frequency [Ghz] Max. Memory Frequency [MHz] TDP [Watt] Celeron G n/a n/a Celeron G n/a n/a Pentium G n/a n/a Core i n/a n/a Xeon E3-1220LV Xeon E3-1220V Xeon E3-1265LV Xeon E3-1230V Xeon E3-1240V Xeon E3-1270V Xeon E3-1280V Memory modules (since system release) Memory module 2GB (1x2GB) 1Rx8 DDR U ECC (2 GB 1Rx8 PC E) 4GB (1x4GB) 2Rx8 DDR U ECC (4 GB 2Rx8 PC E) 8GB (1x8GB) 2Rx8 DDR U ECC (8 GB 2Rx8 PC E) Power supplies (since system release) PY RX100S7p/LFF/Standard PSU, PY RX100S7p/SFF/Standard PSU: Standard-PSU 300W PY RX100S7p/LFF/Hot-Plug PSU, PY RX100S7p/SFF/Hot-Plug PSU: Modular PSU 450W platinum hp Max. number 1 2 Some components may not be available in all countries or sales regions. Detailed technical information is available in the data sheet PRIMERGY RX100 S7p. Page 4 (24) Fujitsu Technology Solutions 2012

5 SPECcpu2006 Benchmark description SPECcpu2006 is a benchmark which measures the system efficiency with integer and floating-point operations. It consists of an integer test suite (SPECint2006) containing 12 applications and a floating-point test suite (SPECfp2006) containing 17 applications. Both test suites are extremely computing-intensive and concentrate on the CPU and the memory. Other components, such as Disk I/O and network, are not measured by this benchmark. SPECcpu2006 is not tied to a special operating system. The benchmark is available as source code and is compiled before the actual measurement. The used compiler version and their optimization settings also affect the measurement result. SPECcpu2006 contains two different performance measurement methods: the first method (SPECint2006 or SPECfp2006) determines the time which is required to process single task. The second method (SPECint_rate2006 or SPECfp_rate2006) determines the throughput, i.e. the number of tasks that can be handled in parallel. Both methods are also divided into two measurement runs, base and peak which differ in the use of compiler optimization. When publishing the results the base values are always used; the peak values are optional. Benchmark Arithmetics Type Compiler optimization SPECint2006 integer peak aggressive SPECint_base2006 integer base conservative SPECint_rate2006 integer peak aggressive SPECint_rate_base2006 integer base conservative SPECfp2006 floating point peak aggressive SPECfp_base2006 floating point base conservative SPECfp_rate2006 floating point peak aggressive SPECfp_rate_base2006 floating point base conservative Measurement result Speed Throughput Speed Throughput Application single-threaded multi-threaded single-threaded multi-threaded The measurement results are the geometric average from normalized ratio values which have been determined for individual benchmarks. The geometric average - in contrast to the arithmetic average - means that there is a weighting in favour of the lower individual results. Normalized means that the measurement is how fast is the test system compared to a reference system. Value 1 was defined for the SPECint_base2006-, SPECint_rate_base2006, SPECfp_base2006 and SPECfp_rate_base2006 results of the reference system. For example, a SPECint_base2006 value of 2 means that the measuring system has handled this benchmark twice as fast as the reference system. A SPECfp_rate_base2006 value of 4 means that the measuring system has handled this benchmark some 4/[# base copies] times faster than the reference system. # base copies specify how many parallel instances of the benchmark have been executed. Not every SPECcpu2006 measurement is submitted by us for publication at SPEC. This is why the SPEC web pages do not have every result. As we archive the log files for all measurements, we can prove the correct implementation of the measurements at any time. Fujitsu Technology Solutions 2012 Page 5 (24)

6 Benchmark environment System Under Test (SUT) Hardware Model Memory Software BIOS settings PRIMERGY RX100 S7p Celeron G500 processor series Pentium G640 Core i Xeon E processor series 2 8GB (1x8GB) 2Rx8 L DDR U ECC SPECint_base2006, SPECint2006, SPECfp_base2006, SPECfp2006: s other than Celeron G500 processor series, Pentium G640, Xeon E3-1220V2: Hyper-Threading = Disable Operating system Red Hat Enterprise Linux Server release 6.2 Operating system settings echo always > /sys/kernel/mm/redhat_transparent_hugepage/enabled Compiler Intel C++/Fortran Compiler 12.1 Some components may not be available in all countries or sales regions. Page 6 (24) Fujitsu Technology Solutions 2012

7 SPECfp_base2006 SPECfp2006 SPECfp_rate_base2006 SPECfp_rate2006 SPECint_base2006 SPECint2006 SPECint_rate_base2006 SPECint_rate2006 WHITE PAPER PERFORMANCE REPORT PRIMERGY RX100 S7P VERSION: Benchmark results In terms of processors the benchmark result depends primarily on the size of the processor cache, the support for Hyper-Threading, the number of processor cores and on the processor frequency. In the case of processors with Turbo mode the number of cores, which are loaded by the benchmark, determines the maximum processor frequency that can be achieved. In the case of single-threaded benchmarks, which largely load one core only, the maximum processor frequency that can be achieved is higher than with multithreaded benchmarks (see the processor table in the section "Technical Data"). Celeron G Celeron G Pentium G Core i Xeon E3-1220LV Xeon E3-1220V Xeon E3-1265LV Xeon E3-1230V Xeon E3-1240V Xeon E3-1270V Xeon E3-1280V Celeron G Celeron G Pentium G Core i Xeon E3-1220LV Xeon E3-1220V Xeon E3-1265LV Xeon E3-1230V Xeon E3-1240V Xeon E3-1270V Xeon E3-1280V Fujitsu Technology Solutions 2012 Page 7 (24)

8 The following four diagrams illustrate the throughput of the PRIMERGY RX100 S7p in comparison to its predecessor PRIMERGY RX100 S7, in their respective most performant configuration. SPECcpu2006: integer performance PRIMERGY RX100 S7p vs. PRIMERGY RX100 S SPECint SPECint_base PRIMERGY RX100 S7 Xeon E PRIMERGY RX100 S7p Xeon E3-1280V2 SPECcpu2006: integer performance PRIMERGY RX100 S7p vs. PRIMERGY RX100 S SPECint_rate2006 SPECint_rate_base PRIMERGY RX100 S7 Xeon E PRIMERGY RX100 S7p Xeon E3-1280V2 Page 8 (24) Fujitsu Technology Solutions 2012

9 SPECcpu2006: floating-point performance PRIMERGY RX100 S7p vs. PRIMERGY RX100 S SPECfp SPECfp_base PRIMERGY RX100 S7 Xeon E PRIMERGY RX100 S7p Xeon E3-1280V2 SPECcpu2006: floating-point performance PRIMERGY RX100 S7p vs. PRIMERGY RX100 S SPECfp_rate SPECfp_rate_base PRIMERGY RX100 S7 Xeon E PRIMERGY RX100 S7p Xeon E3-1280V2 Fujitsu Technology Solutions 2012 Page 9 (24)

10 SPECjbb2005 Benchmark description SPECjbb2005 is a Java business benchmark that focuses on the performance of Java Server platforms. SPECjbb2005 is essentially a modernized SPECjbb2000. The main differences are: The transactions have become more complex in order to cover a greater functional scope. The working set of the benchmark has been enlarged to the extent that the total system load has increased. SPECjbb2000 allows only one active Java Virtual Machine instance (JVM) whereas SPECjbb2005 permits several instances, which in turn achieves greater closeness to reality, particularly with large systems. On the software side SPECjbb2005 primarily measures the performance of the JVM used with its just-in-time compiler as well as their thread and garbage collection implementation. Some aspects of the operating system used also play a role. As far as hardware is concerned, it measures the efficiency of the CPUs and caches, the memory subsystem and the scalability of shared memory systems (SMP). Disk and network I/O are irrelevant. SPECjbb2005 emulates a 3-tier client/server system that is typical for modern business process applications with the emphasis on the middle-tier system: Clients generate the load, consisting of driver threads, which on the basis of TPC-C benchmark generate OLTP accesses to a database without thinking times. The middle tier system implements the business processes and the updating of the database. The database takes on the data management and is emulated by Java objects that are in the memory. Transaction logging is implemented on an XML basis. The major advantage of this benchmark is that it includes all three tiers that run together on a single host. The performance of the middle-tier is measured. Large-scale hardware installations are thus avoided and direct comparisons between the SPECjbb2005 results from the various systems are possible. Client and database emulation are also written in Java. SPECjbb2005 only needs the operating system as well as a Java Virtual Machine with J2SE 5.0 features. The scaling unit is a warehouse with approx. 25 MB Java objects. Precisely one Java thread per warehouse executes the operations on these objects. The business operations are assumed by TPC-C: New Order Entry Payment Order Status Inquiry Delivery Stock Level Supervision Customer Report However, these are the only features SPECjbb2005 and TPC-C have in common. The results of the two benchmarks are not comparable. SPECjbb2005 has 2 performance metrics: bops (business operations per second) is the overall rate of all business operations performed per second. bops/jvm is the ratio of the first metrics and the number of active JVM instances. In comparisons of various SPECjbb2005 results, both metrics must be specified. The following rules, according to which a compliant benchmark run has to be performed, are the basis for these three metrics: A compliant benchmark run consists of a sequence of measuring points with an increasing number of warehouses (and thus of threads) with the number in each case being increased by one warehouse. The run is started at one warehouse up through 2*MaxWh, but not less than 8 warehouses. MaxWh is the number of warehouses with the highest rate per second the benchmark expects. Per default the benchmark equates MaxWh with the number of CPUs visible by the operating system. The metric bops is the arithmetic average of all measured operation rates with MaxWh warehouses up to 2*MaxWh warehouses. Page 10 (24) Fujitsu Technology Solutions 2012

11 Benchmark environment System Under Test (SUT) Hardware Model Memory Software BIOS settings Operating system Operating system settings JVM PRIMERGY RX100 S7p Xeon E3-1280V2 4 4GB (1x4GB) 2Rx8 DDR U ECC Hardware Prefetch = Disable Adjacent Sector Prefetch = Disable Microsoft Windows Server 2008 R2 Enterprise SP1 Using the local security settings console, "lock pages in memory" was enabled for the user running the benchmark. Oracle Java HotSpot(TM) 64-Bit Server VM on Windows, version 1.6.0_31 JVM settings start /AFFINITY [0x0F,0xF0] java -server -Xmx6g -Xms6g -Xmn5g -XX:SurvivorRatio=60 - XX:TargetSurvivorRatio=90 -XX:ParallelGCThreads=4 -XX:AllocatePrefetchDistance=256 - XX:AllocatePrefetchLines=4 -XX:LoopUnrollLimit=45 -XX:InitialTenuringThreshold=12 - XX:MaxTenuringThreshold=15 -XX:InlineSmallCode=3900 -XX:MaxInlineSize=270 - XX:FreqInlineSize=2500 -XX:+UseLargePages -XX:+UseParallelOldGC - XX:+UseCompressedStrings -XX:+AggressiveOpts Some components may not be available in all countries or sales regions. Benchmark results SPECjbb2005 bops = SPECjbb2005 bops/jvm = The PRIMERGY RX100 S7p achieved the best SPECjbb2005 result of all Intel based 1-socket servers (Status of: May, 14 th 2012). For the latest SPECjbb2005 results, visit The following diagrams illustrate the throughput of the PRIMERGY RX100 S7p in comparison to its predecessor PRIMERGY RX100 S7, in their respective most performant configuration. SPECjbb2005 bops: PRIMERGY RX100 S7p vs. RX100 S7 SPECjbb2005 bops: PRIMERGY RX100 S7p vs. RX100 S7 Fujitsu Technology Solutions 2012 Page 11 (24)

12 SPECpower_ssj2008 Benchmark description SPECpower_ssj2008 is the first industry-standard SPEC benchmark that evaluates the power and performance characteristics of a server. With SPECpower_ssj2008 SPEC has defined standards for server power measurements in the same way they have done for performance. The benchmark workload represents typical server-side Java business applications. The workload is scalable, multi-threaded, portable across a wide range of platforms and easy to run. The benchmark tests CPUs, caches, the memory hierarchy and scalability of symmetric multiprocessor systems (SMPs), as well as the implementation of Java Virtual Machine (JVM), Just In Time (JIT) compilers, garbage collection, threads and some aspects of the operating system. SPECpower_ssj2008 reports power consumption for servers at different performance levels from 100% to active idle in 10% segments over a set period of time. The graduated workload recognizes the fact that processing loads and power consumption on servers vary substantially over the course of days or weeks. To compute a power-performance metric across all levels, measured transaction throughputs for each segment are added together and then divided by the sum of the average power consumed for each segment. The result is a figure of merit called overall ssj_ops/watt. This ratio provides information about the energy efficiency of the measured server. The defined measurement standard enables customers to compare it with other configurations and servers measured with SPECpower_ssj2008. The diagram shows a typical graph of a SPECpower_ssj2008 result. The benchmark runs on a wide variety of operating systems and hardware architectures and does not require extensive client or storage infrastructure. The minimum equipment for SPEC-compliant testing is two networked computers, plus a power analyzer and a temperature sensor. One computer is the System Under Test (SUT) which runs one of the supported operating systems and the JVM. The JVM provides the environment required to run the SPECpower_ssj2008 workload which is implemented in Java. The other computer is a Control & Collection System (CCS) which controls the operation of the benchmark and captures the power, performance and temperature readings for reporting. The diagram provides an overview of the basic structure of the benchmark configuration and the various components. Page 12 (24) Fujitsu Technology Solutions 2012

13 Benchmark environment System Under Test (SUT) Hardware Model Model version Memory Network-Interface Disk-Subsystem Software PRIMERGY RX100 S7p PY RX100S7p/SFF/Standard PSU Xeon E3-1265LV2 BIOS BIOS: R1.7.0 FW: 6.50 BIOS settings Operating system Operating system settings JVM JVM settings 2 4GB (1x4GB) 2Rx8 L DDR U ECC Onboard LAN-Controller (1 port used) Onboard HDD-Controller 1 SSD SATA 3G 32GB SLC HOT PLUG 2.5" EP Adjacent Sector Prefetch = Disabled Hardware Prefetch = Disabled SATA Mode Selection = AHCI Mode USB Port Control = Disable all Ports P-State coordination = SW_ANY Intel Virtualization Technology = Disabled ASPM Support = Auto LAN Port 1 = Disable Microsoft Windows Server 2008 R2 Enterprise SP1 Using the local security settings console, lock pages in memory was enabled for the user running the benchmark. Power Management: Enabled ( Fujitsu Enhanced Power Settings power plan) Set Turn off hard disk after = 1 Minute in OS. Benchmark was started via Windows Remote Desktop Connection. Oracle Java HotSpot(TM) 64-Bit Server VM on Windows, version 1.6.0_31 -server -Xmx1024m -Xms1024m -Xmn853m -XX:ParallelGCThreads=2 -XX:SurvivorRatio=60 -XX:TargetSurvivorRatio=90 -XX:InlineSmallCode=3900 -XX:MaxInlineSize=270 -XX:FreqInlineSize=2500 -XX:AllocatePrefetchDistance=256 -XX:AllocatePrefetchLines=4 -XX:InitialTenuringThreshold=12 -XX:MaxTenuringThreshold=15 -XX:LoopUnrollLimit=45 -XX:+UseCompressedStrings -XX:+AggressiveOpts -XX:+UseLargePages -XX:+UseParallelOldGC Some components may not be available in all countries or sales regions. Fujitsu Technology Solutions 2012 Page 13 (24)

14 Benchmark results The PRIMERGY RX100 S7p achieved the following result: SPECpower_ssj2008 = 5,576 overall ssj_ops/watt The adjoining diagram shows the result of the configuration described above. The red horizontal bars show the performance to power ratio in ssj_ops/watt (upper x-axis) for each target load level tagged on the y-axis of the diagram. The blue line shows the run of the curve for the average power consumption (bottom x-axis) at each target load level marked with a small rhomb. The black vertical line shows the benchmark result of 5,576 overall ssj_ops/watt for the PRIMERGY RX100 S7p. This is the quotient of the sum of the transaction throughputs for each load level and the sum of the average power consumed for each measurement interval. The following table shows the benchmark results for the throughput in ssj_ops, the power consumption in watts and the resulting energy efficiency for each load level. Performance Power Energy Efficiency Target Load ssj_ops Average Power (W) ssj_ops/watt 100% 416, ,013 90% 376, ,614 80% 331, ,559 70% 289, ,772 60% 250, ,614 50% 207, ,016 40% 166, ,281 30% 125, ,352 20% 82, ,185 10% 41, ,796 Active Idle ssj_ops / power = 5,576 The PRIMERGY RX100 S7p achieved a new class record with this result, thus surpassing the best result of the competition by 10% (date: May 14, 2012). Thus, the PRIMERGY RX100 S7p proves itself to be the most energy-efficient rack server in the world. For the latest SPECpower_ssj2008 benchmark results, visit: Page 14 (24) Fujitsu Technology Solutions 2012

15 SPECpower_ssj2008: PRIMERGY RX100 S7p vs. competition The adjoining chart shows the comparison to the competition and makes the advantage of the PRIMERGY RX100 S7p in the field of energy efficiency evident. Compared to the so far best result of the competition, the Huawei RH2288 V2, the PRIMERGY RX100 S7p achieves a result with 10% higher energy efficiency. The following diagram shows for each load level the power consumption (on the right y-axis) and the throughput (on the left y-axis) of the PRIMERGY RX100 S7p compared to the predecessor the PRIMERGY RX100 S7. SPECpower_ssj2008: PRIMERGY RX100 S7p vs. PRIMERGY RX100 S7 Fujitsu Technology Solutions 2012 Page 15 (24)

16 Thanks to the new Ivy-Bridge processor generation the PRIMERGY RX100 S7p has in comparison with the PRIMERGY RX100 S7 a substantially higher throughput at almost identical power consumption. This results in an overall increase in energy efficiency in the PRIMERGY RX100 S7p of 29%. SPECpower_ssj2008 overall ssj_ops/watt: PRIMERGY RX100 S7p vs. PRIMERGY RX100 S7 Page 16 (24) Fujitsu Technology Solutions 2012

17 OLTP-2 Benchmark description OLTP stands for Online Transaction Processing. The OLTP-2 benchmark is based on the typical application scenario of a database solution. In OLTP-2 database access is simulated and the number of transactions achieved per second (tps) determined as the unit of measurement for the system. In contrast to benchmarks such as SPECint and TPC-E, which were standardized by independent bodies and for which adherence to the respective rules and regulations are monitored, OLTP-2 is an internal benchmark of Fujitsu. OLTP-2 is based on the well-known database benchmark TPC-E. OLTP-2 was designed in such a way that a wide range of configurations can be measured to present the scaling of a system with regard to the CPU and memory configuration. Even if the two benchmarks OLTP-2 and TPC-E simulate similar application scenarios using the same load profiles, the results cannot be compared or even treated as equal, as the two benchmarks use different methods to simulate user load. OLTP-2 values are typically similar to TPC-E values. A direct comparison, or even referring to the OLTP-2 result as TPC-E, is not permitted, especially because there is no priceperformance calculation. Further information can be found in the document Benchmark Overview OLTP-2. Benchmark environment The measurement set-up is symbolically illustrated below: Driver Tier A Tier B Network Network Application Server Database Server Disk subsystem Clients System Under Test (SUT) Fujitsu Technology Solutions 2012 Page 17 (24)

18 The results presented here are valid for all the PRIMERGY systems in the following configuration: Database Server (Tier B) Hardware Celeron G530, G550 Pentium G640 Core i Xeon E processor series Memory 32 GB: 4 8 GB (1x8GB) 2Rx8 DDR U ECC Network interface 2 onboard LAN 1 Gb/s Disk subsystem RAID 0 (OS) Operating system and database application RAID 1 (LOG) Sequential access, optimized to short response times RAID 5 (data) Random access, optimized to throughput Software Operating system Database Microsoft Windows Server 2008 R2 Standard Microsoft SQL Server 2008 R2 Standard Application Server (Tier A) Hardware Model Memory Network interface Disk subsystem Software Operating system 1 PRIMERGY RX200 S6 2 Xeon X GB, 1333 MHz registered ECC DDR3 2 onboard LAN 1 Gb/s 2 Dual Port LAN 1Gb/s 1 73 GB 15k rpm SAS Drive Microsoft Windows Server 2008 R2 Standard Client Hardware Model 1 PRIMERGY RX200 S5 2 Xeon X5570 Memory 24 GB, 1333 MHz registered ECC DDR3 Network interface 2 onboard LAN 1 Gb/s Disk subsystem 1 73 GB 15k rpm SAS Drive Software Operating system Microsoft Windows Server 2008 R2 Standard Benchmark OLTP-2 Software EGen version Some components may not be available in all countries / sales regions. Page 18 (24) Fujitsu Technology Solutions 2012

19 Benchmark results Database performance greatly depends on the configuration options with CPU, memory and on the connectivity of an adequate disk subsystem for the database. In the following scaling considerations for the processors we assume that both the memory and the disk subsystem has been adequately chosen and is not a bottleneck. A guideline in the database environment for selecting main memory is that sufficient quantity is more important than the speed of the memory accesses. For this reason the maximum configuration with 8 GB modules was considered. The following diagram shows the OLTP-2 transaction rates that can be achieved with one processor of the processor types under review here. OLTP-2 tps bold: measured cursive: calculated Xeon E3-1280V2 4 Core, HT Xeon E3-1270V2 4 Core, HT Xeon E3-1240V2 4 Core, HT Xeon E3-1230V2 4 Core, HT Xeon E3-1265LV2 4 Core, HT Xeon E3-1220V2 4 Core Xeon E3-1220LV2 2 Core, HT Core i Core, HT Pentium G640 2 Core Celeron G550 2 Core Celeron G530 2 Core HT: Hyper-Threading tps It is evident that a wide performance range is covered by the variety of released processors. If you compare the OLTP-2 value of the processor with the lowest performance (Celeron G530) with the value of the processor with the highest performance (Xeon E3-1280V2), the result is a 4-fold increase in performance. Based on the results achieved and the technical features the processors can be divided into different performance groups: Celeron and Pentium as the processors with two cores only and without Hyper-Threading make the start. The next performance group of processors achieves a higher performance in the OLTP-2 scenario. This is the processor with two cores and without turbo mode (Core i3-3220). In the group of Xeon E3 processors the Xeon E3-1220LV2 with its two processor cores and an L3 cache of only 3 MB is at the lower end of the performance scale, but the power consumption with 17 W TDP is the smallest of all the processors under review here. The processors with four cores achieve a considerably better performance, because typically under the OLTP-2 load, doubling the number of cores almost results in twice the performance. Doubling the logical processor cores through Hyper-Threading also leads to better results under the OLTP-2 load, which explains the leap in performance of the Xeon E3-1220V2 CPU without Hyper-Threading to the Xeon E3-1230V2 processor with Hyper-Threading. Fujitsu Technology Solutions 2012 Page 19 (24)

20 STREAM Benchmark description STREAM is a synthetic benchmark that has been used for many years to determine memory throughput and which was developed by John McCalpin during his professorship at the University of Delaware. Today STREAM is supported at the University of Virginia, where the source code can be downloaded in either Fortran or C. STREAM continues to play an important role in the HPC environment in particular. It is for example an integral part of the HPC Challenge benchmark suite. The benchmark is designed in such a way that it can be used both on PCs and on server systems. The unit of measurement of the benchmark is GB/s, i.e. the number of gigabytes that can be read and written per second. STREAM measures the memory throughput for sequential accesses. These can generally be performed more efficiently than accesses that are randomly distributed on the memory, because the CPU caches are used for sequential access. Before execution the source code is adapted to the environment to be measured. Therefore, the size of the data area must be at least four times larger than the total of all CPU caches so that these have as little influence as possible on the result. The OpenMP program library is used to enable selected parts of the program to be executed in parallel during the runtime of the benchmark, consequently achieving optimal load distribution to the available processor cores. During implementation the defined data area, consisting of 8-byte elements, is successively copied to four types, and arithmetic calculations are also performed to some extent. Type Execution Bytes per step Floating-point calculation per step COPY a(i) = b(i) 16 0 SCALE a(i) = q b(i) 16 1 SUM a(i) = b(i) + c(i) 24 1 TRIAD a(i) = b(i) + q c(i) 24 2 The throughput is output in GB/s for each type of calculation. The differences between the various values are usually only minor on modern systems. In general, only the determined TRIAD value is used as a comparison. The measured results primarily depend on the clock frequency of the memory modules; the CPUs influence the arithmetic calculations. The accuracy of the results is approximately 5%. This chapter specifies throughputs on a basis of 10 (1 GB/s = 10 9 Byte/s). Benchmark environment System Under Test (SUT) Hardware Model Memory Software BIOS settings PRIMERGY RX100 S7p Celeron G530, G550 Pentium G640 Core i Xeon E processor series 2 8GB (1x8GB) 2Rx8 L DDR U ECC Hyper-Threading = Disabled Operating system Red Hat Enterprise Linux Server release 6.2 Operating system settings Compiler Intel C Compiler 12.1 Benchmark Stream.c Version 5.9 echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled Some components may not be available in all countries or sales regions. Page 20 (24) Fujitsu Technology Solutions 2012

21 Benchmark results Max. Memory Frequency [MHz] TRIAD [GB/s] Celeron G Celeron G Pentium G Core i Xeon E3-1220LV Xeon E3-1220V Xeon E3-1265LV Xeon E3-1230V Xeon E3-1240V Xeon E3-1270V Xeon E3-1280V The results depend primarily on the maximum memory frequency. The following diagram illustrates the throughput of the PRIMERGY RX100 S7p in comparison to its predecessor, the PRIMERGY RX100 S7, in their most performant configuration. STREAM TRIAD: PRIMERGY RX100 S7p vs. PRIMERGY RX100 S7 GB/s PRIMERGY RX100 S7 PRIMERGY RX100 S7p Xeon E Xeon E3-1280V2 Fujitsu Technology Solutions 2012 Page 21 (24)

22 LINPACK Benchmark description LINPACK was developed in the 1970s by Jack Dongarra and some other people to show the performance of supercomputers. The benchmark consists of a collection of library functions for the analysis and solution of linear system of equations. A description can be found in the document LINPACK can be used to measure the speed of a computer during the solution of an N dimensional linear system of equations. The result is specified in GFlops (Giga Floating Point Operations per Second). It is a measure of how many floating-point operations can be carried out per second. The number of floating-point operations required for the solution is determined by the formula 2 / 3 N N 2. For the calculation LINPACK requires a matrix of size N N in the main memory with the value N standing for the number of equations to be solved. Maximum performance is achieved if the available main memory can be fully used as a result of choosing this value. However, the determination of this limit is very timeconsuming and the expected increase in the result is only minor. The memory bandwidth of the system also has hardly any impact on the result, because floating-point calculations are chiefly carried out during the run and data exchange only seldom takes place between the parallel processes. Thus the benchmark result is determined for a value of N that is somewhat below the maximum value. LINPACK is classed as one of the leading benchmarks in the field of high performance computing (HPC). LINPACK is one of the seven benchmarks currently included in the HPC Challenge benchmark suite, which takes other performance aspects in the HPC environment into account. Intel offers a LINPACK version that has been highly optimized for individual systems with Intel processors. The optimal parameter values are autonomously determined by the software on the basis of the current processor architecture. Another version provided by Intel is based on hpl (High-Performance Linpack) for use on distributed systems, with the intercommunication of the servers taking place via Message Passing Interface (MPI). In the case of this version the parameter values are set via a configuration file. Both versions can be downloaded from It is possible to publish LINPACK results at Prerequisite for this is the use of an MPIbased (Message Passing Interface) version. (See: The maximum theoretical performance of a processor core follows from the number of floating-point operations that are performed within a clock cycle. Thus e.g. a single processor core with a clock frequency of 2.4 GHz and 4 floating-point operations per cycle would achieve a maximum performance of 9.6 GFlops. The ratio of the measured result to the maximum value shows the efficiency of the system for floating-point calculations. The fewer memory accesses required during the calculation, the better the ratio. Benchmark environment System Under Test (SUT) Hardware Model Memory Software BIOS settings PRIMERGY RX100 S7p Celeron G500 processor series Pentium G640 Core i Xeon E processor series 2 8GB (1x8GB) 2Rx8 L DDR U ECC Hyper-Threading = Disabled Operating system Red Hat Enterprise Linux Server release 6.2 Benchmark xlinpack_xeon64 from Intel Compiler 12.1 Some components may not be available in all countries or sales regions. Page 22 (24) Fujitsu Technology Solutions 2012

23 Benchmark results The available main memory of 16 GB permits a dimension of N = Cores frequency [Ghz] Maximum turbo frequency at full load [Ghz] Theoretical maximum [GFlops] LINPACK [GFlops] Efficiency Celeron G n/a Celeron G n/a Pentium G n/a Core i n/a Xeon E3-1220LV Xeon E3-1220V Xeon E3-1265LV Xeon E3-1230V Xeon E3-1240V Xeon E3-1270V Xeon E3-1280V [%] A theoretical maximum value can be calculated for processors without Turbo mode with the formula GFlops max = Number of floating-point operations per clock cycle Number of processor cores frequency[ghz] s that have Turbo mode are not limited by the nominal processor frequency and therefore do not provide a constant processor frequency. In this case, the actual processor frequency lies between the nominal processor frequency and the maximum turbo frequency at full load. To calculate the theoretical maximum the following formula is used for these processors: GFlops max = Number of floating-point operations per clock cycle Number of processor cores Maximum turbo frequency at full load[ghz] The following diagram illustrates the throughput of the PRIMERGY RX100 S7p in comparison to its predecessor, the PRIMERGY RX100 S7, in their most performant configuration. GFlops LINPACK: PRIMERGY RX100 S7p vs. PRIMERGY RX100 S PRIMERGY RX100 S7 PRIMERGY RX100 S7p Xeon E Xeon E3-1280V2 Fujitsu Technology Solutions 2012 Page 23 (24)

24 Literature PRIMERGY Systems PRIMERGY RX100 S7p Data sheet RAID Controller Performance Single Disk Performance PRIMERGY Performance LINPACK OLTP-2 Benchmark Overview OLTP-2 SPECcpu Benchmark overview SPECcpu SPECjbb Benchmark overview SPECjbb SPECpower_ssj Benchmark Overview SPECpower_ssj STREAM Contact FUJITSU Website: PRIMERGY Product Marketing PRIMERGY Performance and Benchmarks All rights reserved, including intellectual property rights. Technical data subject to modifications and delivery subject to availability. Any liability that the data and illustrations are complete, actual or correct is excluded. Designations may be trademarks and/or copyrights of the respective manufacturer, the use of which by third parties for their own purposes may infringe the rights of such owner. For further information see WW EN Copyright Fujitsu Technology Solutions 2012 Page 24 (24) Fujitsu Technology Solutions 2012