Technical data

White Paper Performance Report PRIMERGY TX150 S6 Version: 5.1, November 2008
As you can see the most energy efficient configuration does not consume the lowest power. It is still about 108% more
efficient compared to the least energy efficient configuration. The configuration with the Xeon E3120 processor has the
lowest power consumption. Although the best configuration with the Xeon X3360 processor does not deliver the highest
throughput in ssj_ops and does not have the lowest power consumption, it achieves the highest benchmark score of
1,124 overall ssj_ops/watt.
The other results are important too, as they show the dependencies between the configurations and the efficiency. This
information should give some hints about the power consumption and efficiency that can be expected from real world
configurations used in customer installations.
Benchmark environment
All SPECpower_ssj2008 measurements presented here were performed on a PRIMERGY TX150 S6 with the following
hardware and software configuration using the ZES Zimmer LMG95 power analyzer:
Hardware
Model PRIMERGY TX150 S6
Processor (TDP) Xeon E3120 (65 W), X3220 (95 W), X3360 (95 W), X3370 (95 W)
Number of chips 1 chip, 2 cores per chip and 4 cores per chip
Primary Cache 32 KB instruction + 32 KB data on chip, per core
Secondary Cache 8 MB (I+D) on chip, per chip and 12 MB (I+D) on chip, per chip (6 MB shared / 2 cores)
Other Cache none
Memory
2 x 2 GB PC2-6400E DDR2-SDRAM
4 x 2 GB PC2-6400E DDR2-SDRAM
Network Interface 1 x 1 GBit LAN Broadcom (onboard)
Disk Subsystem
1 × Integrated SATA Controller
1 × 3.5” SATA disk, 160 GB, 7.2 krpm, JBOD
4 × 3.5” SATA disk, 160 GB, 7.2 krpm, JBOD
Power Supply Unit
1 x 350 W DPS-350UB A
1 x 450 W DPS-450FB G
2 x 450 W DPS-450FB G
Software
Operating System Windows Server 2003 R2 Enterprise x64 Edition
JVM Version
Oracle JRockit(R) 6.0 P27.5.0
(build P27.5.0-5_o_CR371811_CR374296-100684-1.6.0_03-20080702-1651-windows-x86_64)
JVM options
-Xms1650m -Xmx1650m -Xns1500m -XXaggressive -Xlargepages -Xgc:genpar -XXcallprofiling
-XXgcthreads=2 -XXtlasize:min=4k,preferred=1024k -XXthroughputcompaction
© Fujitsu Technology Solutions 2009 Page 16 (33)