Server Performance Summary
IT cost optimization starts with server performance
New x86 two socket server world recordsΔ
| Highlights on Intel® Xeon® processor 5600 series-based server (April 2011 ) | ||||
|---|---|---|---|---|
| Segment - Benchmark | Platform/Partner | Software Details | Result (gain over Intel® Xeon® processor X5570) |
Importance |
| Database - TPC Benchmark* H |
Hewlett-Packard ProLiant DL380 G7* |
SQL Server 2008* database R2, Windows Server 2008 R2* |
73,975 QphH @ $0.58/QphH @ 100GB (+38%) |
Number one non-clustered two-socket SQL server result @ 100GB |
| Database - TPC Benchmark* H |
Dell PowerEdge R710* |
EXASOL EXASolution* 4.0, EXASOL EXACluster* OS 4.0 |
1,112,402 QphH @ $0.12/QphH @ 100GB |
Number one clustered result @ 100GB |
| Database - TPC Benchmark* E |
Fujitsu PRIMERGY RX300 S6* |
SQL Server 2008* database R2, Windows Server 2008 R2* |
1,268.30 TpsE @ $183.94/TpsE (+55%) |
Number one two-socket result |
| Scientific Computing - SPECfp*_base2006 |
Fujitsu PRIMERGY RX300 S6* & Fujitsu PRIMERGY TX300 S6* |
Intel® C++ Compiler 12.0, SUSE Linux Enterprise Server* (SLES) 11 SP1 | 62 (+14%) | Number one two-socket server result |
| Virtualization - VMmark* v1.1.1 |
Fujitsu BX924 S2* | VMware ESX 4.0 U2* | 40.86@30 tiles (+62%) | Number one two-socket result |
| Virtualization - VMmark* v2.0 |
Fujitsu PRIMERGY RX200 S6* | VMware ESX* 4.1 | 7.02@7 tiles | Excellent two-socket result |
| Database - TPC Benchmark* C |
Hewlett-Packard ProLiant DL380 G7* | SQL Server 2005* Enterprise x64 SP3 database, Windows Server 2008 R2* | 803,068 TpmC @ $0.68/TpmC (+27%) | Number one two-socket x86 result |
| Energy Efficiency - SPECpower*_ssj2008 (Single Node Server) |
HP ProLiant DL380 G7* | IBM* J9 JVM | 3,197 overall ssj_ops/watt (+55%) | Number one two-socket single node server result |
| Energy Efficiency - SPECpower*_ssj2008 (Multi-Node Server) |
Hewlett-Packard ProLiant DL170e G6* | IBM* J9 JVM | 3,212 overall ssj_ops/watt (+36%) (gain over Intel® Xeon® processor L5530) | Number one two-socket multi-node server result |
| Energy Efficiency – SAP* Server Power Benchmark (2-tier) |
Fujitsu PRIMERGY RX300 S6* | SAP enhancement package 4 for SAP ERP 6.0, Windows Server 2008 R2* Datacenter Edition | 18.3 watts / kilo SAPS | Number one server result |
| eCommerce - SPECjbb*2005 (Single JVM) |
Sun Fire X4270 M2* | Java HotSpot 1.6.0_21*, Oracle Solaris 10* | 812,358 SPECjbb2005 bops (+59%) | Number one two-socket single JVM result |
| Web Server - SPECWeb*2005 | Fujitsu PRIMERGY TX300 S6* | Rock Web Server* v1.4.7, Red Hat* Enterprise Linux* 5.3 | 104,422(+25%) | Number one two-socket x86 server result |
| HPC - SPEComp*Mbase 2001 |
Cisco UCS B200 M2* | SUSE Linux Enterprise Server* (SLES), Intel® C/C++ Compiler 11.1.059 | 52,986 (+21%) | Number one two-socket x86 server result |
| HPC – SPEComp*Lbase2001 | Cisco UCS B200 M2* | SUSE Linux Enterprise Server* (SLES), Intel® C/C++ Compiler 11.1.059 | 282,771 (+18%) | Number one two-socket server result |
| HPC - SPECMPI* 2007 |
Intel® result server cluster | SUSE Linux Enterprise Server* (SLES) | Excellent cluster scaling | Number one two-socket cluster result |
| Integer Single Task - SPECint*_ base2006 |
Fujitsu PRIMERGY RX300 S6* & Fujitsu PRIMERGY TX300 S6* |
Intel® C++ Compiler 12.0, SUSE Linux Enterprise Server* (SLES) 11 SP1 | 45.3 (+16%) | Number one two-socket server result |
| Energy-Efficiency-Performance/watt using SPECint*_rate _base2006 |
Fujitsu PRIMERGY RX300 S6* | Intel® C++ Compiler 11.1, SLES 11 | Intel® Xeon® processor L5640 uses 30% lower power than Intel® Xeon® processor X5570 at SPECint*_rate_base2006 score of 250 | Same performance as Intel® Xeon® processor X5570 with 30% lower power results for
File Type/Size: ZIP 97.3KB results forFile Type/Size: ZIP 101KB |
| HPC - Black-Scholes* (Financial Services) |
Supermicro* | Black-Scholes | 1.63x speed up over X5570 | Exceptional gain over previous generation |
| Java – SPECjEnterprise*2010 | IBM BladeCenter HS22* (application server) & IBM x3850 X5* (database server) | IBM WebSphere Application Server V7*, IBM DB2* | 2752.06 Enterprise jEnterprise operations per second (+52%) | Number one two socket x86 server result |
| General Purpose Computing - SPECint*_ rate_base2006 |
Cisco UCS B200 M2* | Intel® C++ Compiler 12.0, SUSE Linux Enterprise Server* (SLES) 11 SP1 | 390 (+47%) | Number one two socket x86 server result |
| Scientific Computing - SPECfp*_rate_ base2006 |
Fujitsu PRIMERGY BX922 S2* | Intel® C++ Compiler 12.0, SUSE Linux Enterprise Server* (SLES) 11 SP1 | 267 (+30%) | 30% gain over Intel® Xeon® processor X5570 |
| eCommerce - SPECjbb*2005 |
Sun Blade X6270 M2* | Windows Server 2008 Enterprise Edition R2* (64-bit), Oracle Java Hotspot* VM (JDK 6 Update 25) | 975,257 SPECjbb2005 bops (+54%) (487,629 SPECjbb2005 bops/JVM) |
54% gain over Intel® Xeon® processor X5570 |
| Computer Aided Engineering - ANSYS FLUENT* (single node truck_14m) |
Sun Fire X2270 M2* | SUSE Linux Enterprise Server* (SLES) | 94.8 rating (+32%) | Number one two-socket single node result |
| Application Server - SPECjAppServer* 2004 (Single Node Server) |
Cisco UCS C250 M2* | Oracle WebLogic Server*, Oracle 11g Database*, Oracle Enterprise Linux* | 5,185 JOPS (+30%) | 30% gain over Intel® Xeon® processor X5570 |
Software and workloads used in performance tests may have been optimized for performance only on Intel® microprocessors. Performance tests, such as SYSmark* and MobileMark*, are measured using specific computer systems, components, software, operations, and functions. Any change to any of those factors may cause the results to vary. You should consult other information and performance tests to assist you in fully evaluating your contemplated purchases, including the performance of that product when combined with other products.
Source: Performance comparisons based on published, submitted or approved results as of April 25, 2011.
SPECpower_ssj2008* multi-node server result referenced as published on HP ProLiant DL170e G6* at 3,212 overall ssj_ops/watt. For more information, please see www.spec.org/power_ssj2008/results/res2010q4/power_ssj2008-20101116-00318.html.
SAP* Server Power Benchmark result referenced as submitted for publication at 18.3 watts / kilo SAPS on Fujitsu PRIMERGY RX300 S6, 2 processors / 12 cores / 24 threads, Intel Xeon X5675, 3.06 GHz, 64 KB L1 cache and 256 KB L2 cache per core, 12 MB L3 cache per processor, 72 GB main memory, CSTC Gold 800 W, 2 x 64 GB SSDSA2SH064G1G10.
ANSYS FLUENT* single node truck_14m result was obtained on the Sun Fire X2270 M2* platform with Intel® Xeon® processor X5670 (2.93 GHz, 12MB L3, 6.4 GT/s, 6-core, 95W TDP). Referenced as published at 94.8 rating. Source: www.oracle.com/us/solutions/performance-scalability/x2270m2-single-node-62810-bmark-098131.html as of 28 June 2010.
TPC Benchmark* H result on the Intel® Xeon® processor X5680 was obtained with the HP ProLiant DL380 G7*. Referenced as published at 73,975 QphH @ $0.58/QphH @ 100GB as of 28 July 2010. For more information, please see www.tpc.org/tpch/results/tpch_result_detail.asp?id=110070201.
Result for prior generation comparison on the Intel® Xeon® processor X5570 was obtained with the Sun Fire X4270*. Referenced as published at 53,502 QphH @ $1.14/QphH @ 100GB as of 28 July 2010. For more information, please see www.tpc.org/tpch/results/tpch_result_detail.asp?id=109120701.
TPC Benchmark* H clustered result on the Intel® Xeon® processor X5690 was obtained with the Dell PowerEdge* R710. Referenced as published at 1,112,402 QphH @ $0.12/QphH @ 100GB as of 25 April 2011. For more information, please see: http://www.tpc.org/tpch/results/tpch_result_detail.asp?id=111040504
TPC Benchmark* E comparison to prior generation Intel® Xeon® is based on the best published results on each platform. The best published result with Intel® Xeon® processor X5570 was obtained using TPC Benchmark* E kit 1.7, and the best published result with Intel® Xeon® processor X5690 was obtained using TPC Benchmark* E kit 1.12. Differences in kits may impact performance.
SPECompM* and SPECompL* results on Intel® Xeon® processor 5600 series-based server were obtained using 24 OpenMP threads over two sockets, on Intel® Xeon® processor 5500 series-based server 16 OpenMP threads over two sockets were used, on Intel® Xeon® processor 5400 series-based server 8 OpenMP threads over two sockets were used. For more information see the detailed HPC section.
SPECmpi*M2007 results on Intel® Xeon® processor 5500 and Intel® Xeon® processor 5400 series-based clusters were obtained for power of two MPI rank counts from 16 to 128 in fully-subscribed mode on each cluster node. Results on Intel® Xeon® processor 5600 were obtained on the same node counts in fully-subsribed mode with MPI rank counts from 24 to 192. For more information see the detailed HPC section.
All other configuration details and additional comparisons are available in the detailed section of the website. For all server benchmarks see www.intel.com/performance/server/xeon/server.htm. For HPC see www.intel.com/performance/server/xeon/hpc.htm. For VMmark see www.intel.com/performance/server/xeon/virtualization.htm. For SPECpower_ssj2008 see www.intel.com/performance/server/xeon/eep.htm.
Relative performance is calculated by assigning a baseline value of 1.0 to one benchmark result, and then dividing the actual benchmark result for the baseline platform into each of the specific benchmark results of each of the other platforms, and assigning them a relative performance number that correlates with the performance improvements reported. Intel performance benchmark limitations.
SPEC*, SPECint*, SPECfp*, SPECrate* SPECpower*, SPECjAppServer*, SPECjbb*, SPECjvm*, SPECWeb*, SPECompM*, SPECompL*, and SPECMPI* are trademarks of the Standard Performance Evaluation Corporation. See www.spec.org for more information. TPC-C*, TPC-H*, and TPC-E* are trademarks of the Transaction Processing Council. See www.tpc.org for more information.
Intel® Virtualization Technology requires a computer system with an enabled Intel® processor, BIOS, virtual machine monitor (VMM) and, for some uses, certain platform software enabled for it. Functionality, performance or other benefits will vary depending on hardware and software configurations and may require a BIOS update. Software applications may not be compatible with all operating systems. Please check with your application vendor.
Intel® Hyper-Threading Technology (Intel® HT Technology) requires a computer system with a processor supporting Intel® HT Technology and an Intel® HT Technology-enabled chipset, BIOS, and operating system. Performance will vary depending on the specific hardware and software you use. For more information including details on which processors support Intel® HT Technology, see www.intel.com/products/ht/hyperthreading_more.htm.
Intel® Turbo Boost Technology requires a platform with a processor with Intel Turbo Boost Technology capability. Intel Turbo Boost Technology performance varies depending on hardware, software and overall system configuration. Check with your platform manufacturer on whether your system delivers Intel Turbo Boost Technology. For more information, see www.intel.com/technology/turboboost/.
Intel® processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. See www.intel.com/products/processor_number/ for details.
Intel® products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications. All dates and products specified are for planning purposes only and are subject to change without notice.
Intel does not control or audit the design or implementation of third party benchmarks or Web sites referenced in this document. Intel encourages all of its customers to visit the referenced Web sites or others where similar performance benchmarks are reported and confirm whether the referenced benchmarks are accurate and reflect performance of systems available for purchase.







