WHITE PAPER FUJITSU PRIMERGY SERVERS PERFORMANCE REPORT PRIMERGY CX120 S1

Transcription

1 WHITE PAPER PERFORMANCE REPORT PRIMERGY CX120 S1 WHITE PAPER FUJITSU PRIMERGY SERVERS PERFORMANCE REPORT PRIMERGY CX120 S1 This document contains a summary of the benchmarks executed for the PRIMERGY CX120 S1. The PRIMERGY CX120 S1 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 Contents Document history... 2 Technical data... 3 SPECcpu SPECjbb SPECpower_ssj STREAM Literature Contact Fujitsu Technology Solutions Page 1 (16)

2 Document history Version 1.0 First report version including the benchmark chapters SPECcpu2006 Measurements with Xeon L5630, X5650 and X5670 SPECjbb2005 Measurement with Xeon X5670 SPECpower_ssj2008 Measurement with Xeon L5530 and 1 x SATA 2.5 HDD 5400rpm Version 2.0 New benchmark chapters: STREAM Measurements with Xeon E5606, E5645 and X5675 Updated benchmark chapters: SPECcpu2006 Measurements with Xeon E5606, E5645 and X5675 (Intel C++/Fortran-Compiler 12.0) SPECjbb2005 Measurement with Xeon X5675 Page 2 (16) Fujitsu Technology Solutions

3 Technical data The PRIMERGY CX1000 S1 is a data center rack system with a shared cooling architecture. It offers space for up to 38 PRIMERGY CX120 S1 servers and up to five LAN switches. With only one height unit the PRIMERGY CX120 S1 are particularly space-saving cloud server units. They have an Intel 5500 chip set, two processors of the Intel Xeon 5500 or 5600 series (Quad-Core or Hexa- Core), 8 DIMM slots for up to 64 GB DDR3-SDRAM, two 1-channel GBit LAN controllers, an onboard controller for two 2.5 SATA hard disks and a PCI slot (PCI-Express x16). Detailed technical information is available in the data sheet PRIMERGY CX1000 S1 and in the data sheet PRIMERGY CX120 S1. Fujitsu Technology Solutions Page 3 (16)

4 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. Page 4 (16) Fujitsu Technology Solutions

5 Benchmark results Measurement series 1: The PRIMERGY CX120 S1 was measured with Xeon series 5600 processors. The benchmark programs were compiled with Intel C++/Fortran Compiler 11.1 and run under SUSE Linux Enterprise Server 11 (64-bit). Xeon E MB 800 MHz 80 Watt Xeon L MB 1067 MHz 60 Watt Xeon X MB 1333 MHz 95 Watt SPECint_base2006 SPECint2006 Xeon L MB 1067 MHz 40 Watt Xeon X MB 1333 MHz 95 Watt Xeon X MB 1333 MHz 95 Watt Xeon E MB 800 MHz 80 Watt Xeon L MB 1067 MHz 60 Watt Xeon X MB 1333 MHz 95 Watt SPECint_rate_base2006 SPECint_rate2006 Xeon L MB 1067 MHz 40 Watt Xeon X MB 1333 MHz 95 Watt Xeon X MB 1333 MHz 95 Watt Xeon E MB 800 MHz 80 Watt Xeon L MB 1067 MHz 60 Watt Xeon X MB 1333 MHz 95 Watt SPECfp_base2006 SPECfp2006 Xeon L MB 1067 MHz 40 Watt Xeon X MB 1333 MHz 95 Watt Xeon X MB 1333 MHz 95 Watt Xeon E MB 800 MHz 80 Watt Xeon L MB 1067 MHz 60 Watt Xeon X MB 1333 MHz 95 Watt SPECfp_rate_base2006 SPECfp_rate2006 Xeon L MB 1067 MHz 40 Watt Xeon X MB 1333 MHz 95 Watt Xeon X MB 1333 MHz 95 Watt Fujitsu Technology Solutions Page 5 (16)

6 Measurement series 2: In February 2011 the PRIMERGY CX120 S1 was measured with new additional Xeon series 5600 processors. The following four tables show results, in which all benchmark programs were compiled with the Intel C++/Fortran compiler 12.0 and run under SUSE Linux Enterprise Server 11 SP1 (64-bit). Results denoted as (est.) are estimated values. Xeon E MB 800 MHz 80 Watt Xeon L MB 1067 MHz 60 Watt Xeon X MB 1333 MHz 95 Watt SPECint_base2006 SPECint2006 Xeon E MB 1067 MHz 80 Watt Xeon L MB 1067 MHz 40 Watt 28.2 (est.) 30.0 (est.) Xeon E MB 1333 MHz 80 Watt Xeon X MB 1333 MHz 95 Watt 37.6 (est.) 39.6 (est.) Xeon X MB 1333 MHz 95 Watt 40.3 (est.) 42.4 (est.) Xeon X MB 1333 MHz 95 Watt Xeon E MB 800 MHz 80 Watt Xeon L MB 1067 MHz 60 Watt Xeon X MB 1333 MHz 95 Watt SPECint_rate_base2006 SPECint_rate2006 Xeon E MB 1067 MHz 80 Watt Xeon L MB 1067 MHz 40 Watt 183 (est.) 195 (est.) Xeon E MB 1333 MHz 80 Watt Xeon X MB 1333 MHz 95 Watt 329 (est.) 356 (est.) Xeon X MB 1333 MHz 95 Watt 346 (est.) 375 (est.) Xeon X MB 1333 MHz 95 Watt Xeon E MB 800 MHz 80 Watt Xeon L MB 1067 MHz 60 Watt Xeon X MB 1333 MHz 95 Watt SPECfp_base2006 SPECfp2006 Xeon E MB 1067 MHz 80 Watt Xeon L MB 1067 MHz 40 Watt 40.4 (est.) 43.0 (est.) Xeon E MB 1333 MHz 80 Watt Xeon X MB 1333 MHz 95 Watt 54.0 (est.) 57.4 (est.) Xeon X MB 1333 MHz 95 Watt 57.3 (est.) 60.8 (est.) Xeon X MB 1333 MHz 95 Watt Xeon E MB 800 MHz 80 Watt Xeon L MB 1067 MHz 60 Watt Xeon X MB 1333 MHz 95 Watt SPECfp_rate_base2006 SPECfp_rate2006 Xeon E MB 1067 MHz 80 Watt Xeon L MB 1067 MHz 40 Watt 142 (est.) 147 (est.) Xeon E MB 1333 MHz 80 Watt Xeon X MB 1333 MHz 95 Watt 232 (est.) 241 (est.) Xeon X MB 1333 MHz 95 Watt 244 (est.) 251 (est.) Xeon X MB 1333 MHz 95 Watt Page 6 (16) Fujitsu Technology Solutions

7 Benchmark environment Measurement series 1: All SPECcpu2006 measurements were made on a PRIMERGY CX120 S1 with the following hardware and software configuration: Hardware Model CPU Number of CPUs Primary cache Secondary cache Other cache Software Operating System PRIMERGY CX120 S1 Xeon L5630, X5650, X5670 Xeon L5630:, 8 cores others:, 12 cores 32 KB instruction + 32 KB data on chip, per core 256 KB on chip, per core 12 MB (I+D) on chip, per chip SUSE Linux Enterprise Server 11 (64-bit) Compilers Intel C++/Fortran Compiler 11.1 Measurement series 2: All SPECcpu2006 measurements were made on a PRIMERGY CX120 S1 with the following hardware and software configuration: Hardware Model CPU Number of CPUs Primary cache Secondary cache Other cache Software Operating System PRIMERGY CX120 S1 Xeon E5606, E5645, X5675 Xeon E5606:, 8 cores others:, 12 cores 32 KB instruction + 32 KB data on chip, per core 256 KB on chip, per core 12 MB (I+D) on chip, per chip SUSE Linux Enterprise Server 11 SP1 (64-bit) Compilers Intel C++/Fortran Compiler 12.0 Some components may not be available in all countries or sales regions. Fujitsu Technology Solutions Page 7 (16)

8 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 8 (16) Fujitsu Technology Solutions

9 Benchmark results Measurement 1: In June 2010, the PRIMERGY CX120 S1 with two Xeon X5670 processors was measured with a memory configuration of 48 GB PC R DDR3-SDRAM. The measurement was performed using Windows Server 2008 R2 Enterprise. Six J9 VM instances from IBM were used as JVM. The following result was obtained: SPECjbb2005 bops = SPECjbb2005 bops/jvm = Measurement 2: In January 2011 the PRIMERGY CX120 S1 with two Xeon X5675 processors was measured. Otherwise, the configuration corresponded to that of the measurement in June The following result was obtained: SPECjbb2005 bops = SPECjbb2005 bops/jvm = The following diagrams illustrate the throughput of both measurements on the PRIMERGY CX120 S1. Fujitsu Technology Solutions Page 9 (16)

10 Benchmark environment The SPECjbb2005 measurements were performed on a PRIMERGY CX120 S1 with the following hardware and software configuration: Hardware Model Processor Number of chips Primary Cache PRIMERGY CX120 S1 Xeon X5670, Xeon X5675, 12 cores, 6 cores per chip, 2 threads per core 32 KB instruction + 32 KB data on chip, per core Secondary Cache 256 KB (I+D) on chip, per core Tertiary Cache Memory Software 12 MB (I+D) on chip, per chip 6 x 8 GB PC R DDR3-SDRAM Operating System Windows Server 2008 R2 Enterprise JVM Version IBM J9 VM (build 2.4, JRE IBM J9 2.4 Windows Server 2008 amd64-64 jvmwa6460sr _42924 (JIT enabled, AOT enabled) Some components may not be available in all countries or sales regions. Page 10 (16) Fujitsu Technology Solutions

11 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 Collect and Control 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. Fujitsu Technology Solutions Page 11 (16)

12 Target Load WHITE PAPER PERFORMANCE REPORT PRIMERGY CX120 S1 VERSION: Benchmark results In March 2010 the PRIMERGY CX1000 S1 Cloud extension Unit was measured with 38 PRIMERGY CX120 S1 server nodes each with two Xeon L5530 processors and 8 GB of PC E DDR3-SDRAM memory. The measurement was taken under Windows Server 2008 R2 Enterprise. J9 2.4 VM from IBM was used as JVM. The PRIMERGY CX1000 S1 / CX120 S1 achieved with the Xeon L5530 processors a new record value 1 of 2,320 overall ssj_ops/watt in the Nehalem-based server class and thus exceeded the previous front runner, a HP ProLiant SL2x170z G6. 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% active idle SPECpower_ssj2008: PRIMERGY CX1000 S1 / CX120 S ,000 1,500 2,000 2,500 3,000 3,163 3,057 2,947 2,792 2,590 2,322 1,998 1,618 1, Performance to Power Ratio 2,320 overall ssj_ops/watt 0 1,000 2,000 3,000 4,000 5,000 6,000 Average Active Power (W) The adjoining diagram shows the result of the configuration described above, measured with the PRIMERGY CX1000 S1 / CX120 S1. 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 2,320 overall ssj_ops/ watt for the PRIMERGY CX1000 S1 / CX120 S1. 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% 19,935,560 6,303 3,163 90% 18,067,787 5,910 3,057 80% 16,058,381 5,449 2,947 70% 14,050,984 5,033 2,792 60% 12,042,621 4,650 2,590 50% 10,034,224 4,321 2,322 40% 8,023,246 4,015 1,998 30% 6,021,596 3,721 1,618 20% 4,011,503 3,386 1,185 10% 2,006,467 2, Active Idle 0 1,842 0 ssj_ops / power = 2,320 1 Competitive benchmark results stated above reflect results published as of March 24th, This comparison presented above is based on the most energy-efficient Intel Nehalem-based servers. For the latest SPECpower_ssj2008 benchmark results, visit: Page 12 (16) Fujitsu Technology Solutions

13 The configuration was tuned to get the best possible result for this server in terms of performance per watt. The memory configuration of 4 x 2 GB was selected to meet the criteria of best performance at lowest power consumption by populating only two slots with DIMMS from a total of 3 memory channels per CPU. Using this configuration the benchmark does not attain the full capacity of the available memory bandwidth, but the advantage of less power consumption is much greater than with a full configuration. However, the most important factor in the hardware configuration is the correct choice of the processor. Processors are the part of a server which consumes the most power beside the memory subsystem. For the PRIMERGY CX120 S1 the low voltage quad-core Xeon L5530 processors with a Thermal Design Power (TDP) of 60 watt showed the best efficiency score. Benchmark environment This SPECpower_ssj2008 measurement presented here was made using 3 ZES Zimmer LMG95 power analyzers on a PRIMERGY CX1000 S1 / CX120 S1 with the following hardware and software configuration: Hardware (Shared) Model PRIMERGY CX1000 S1 with 38 x CX120 S1 server nodes Hardware (per node) Processor (TDP) Xeon L5530 (60 W) Number of chips Primary cache Secondary cache Tertiary cache Memory Network interface Disk subsystem Power supply unit, 4 cores per chip, 2 threads per core 32 KB instruction + 32 KB data on chip, per core 256 KB (I+D) on chip, per core 8 MB (I+D) on chip, per chip 4 x 2 GB PC E DDR3-SDRAM 2 x 1 GBit LAN Intel Gigabit Network Connection (onboard) 1 x integrated SATA controller 1 x 2.5 SATA HDD, 160 GB, 5.4 krpm, JBOD 1 x 400 W Fujitsu Technology Solutions DPS-460GP A Software (per node) Operating system Windows Server 2008 R2 Enterprise JVM Version JVM affinity JVM options IBM J9 VM (build 2.4, JRE 6/1/00 IBM J9 2.4 Windows Server 2008 amd64-64 jvmwa6460sr _42924 (JIT enabled, AOT enabled) start /affinity [0xF,0xF0,0xF00,0xF000] -Xaggressive -Xcompressedrefs -Xgcpolicy:gencon -Xmn1400m -Xms1550m - Xmx1550m -XlockReservation -Xnoloa -XtlhPrefetch -Xlp -Xgcthreads4 Some components may not be available in all countries / sales regions Fujitsu Technology Solutions Page 13 (16)

14 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 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 Floating-point calculation per step 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%. Benchmark results The PRIMERGY CX120 S1 was measured with processors from the Xeon 5600 series. The benchmark was compiled using the Intel C compiler 12.0 and performed under SUSE Linux Enterprise Server 11 (64-bit). The data area consisted of 40 million elements, which is equivalent to about 305 MB. TRIAD [GB/s] Xeon E MB 1067 MHz 80 Watt Xeon E MB 1333 MHz 80 Watt Xeon X MB 1333 MHz 95 Watt The results clearly show the difference between the processor with a maximum memory frequency of 1067 MHz and those with 1333 MHz. Since the capacity limit of the memory controller is already reached with 4 threads per CPU, processors with 6 cores do not offer any better memory throughput than processors with 4 cores. Page 14 (16) Fujitsu Technology Solutions

15 Benchmark environment All STREAM measurements were based on a PRIMERGY CX120 S1 with the following hardware and software configuration: Hardware Model PRIMERGY CX120 S1 CPU Xeon E5606, E5645, X5675 : Number of cores Xeon E5606: Xeon E5645, X5675: Primary cache 32 kb instruction + 32 kb data on chip, per core Secondary cache 256 kb on chip, per core Other cache Xeon E5606: 8 MB (I+D) on chip, per chip All others: 12 MB (I+D) on chip, per chip Memory 6 x 8 GB PC R DDR3-SDRAM Software Operating system SUSE Linux Enterprise Server 11 (64-bit) with SP1 Compiler Intel C Compiler 12.0 Benchmark Stream.c Version cores 12 cores Some components may not be available in all countries or sales regions. Fujitsu Technology Solutions Page 15 (16)

16 Literature PRIMERGY Systems PRIMERGY CX1000 S1 Data sheet PRIMERGY CX120 S1 Data sheet Memory performance of Xeon 5600 (Westmere-EP)-based systems PRIMERGY Performance SPECcpu Benchmark overview SPECcpu SPECjbb Benchmark overview SPECjbb SPECpower_ssj Benchmark overview SPECpower_ssj STREAM Contact FUJITSU Technology Solutions 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 GmbH Page 16 (16) Fujitsu Technology Solutions