Born to Run Benchmarks
With apologies to Bruce, you can’t start a fire with a SPARC. A fire of proof points, that is.
In two different instances Oracle’s recent announcements on SPARC benchmark data have been lacking — and certainly couldn’t start any flame of passion at OpenWorld.
The first involved the announcement of the SPARC M6-32 server and engineered system. The press release only had a footnote for “estimated” performance of some mysterious sort. Oracle’s benchmark website actually discussed some benchmarks for this new system — but 1) there was no competitive information and 2) they were on Oracle’s very own benchmarks.
In the second case, the SPARC T5-8 was highlighted on the Java end-to-end SPECjEnterprise2010 benchmark. A record was claimed — in actuality, the IBM Power 780 had 19% greater overall performance and 49% greater application server performance per core than the Oracle system.(1)
Additionally, keep in mind that whenever costs are presented in Oracle’s comparisons, they need to be scrutinized to the highest degree. What storage is included, what software is included, what support and maintenance is included? Is an apple being compared to a pineapple?
(P.S. After I wrote this I discovered that today is actually Bruce Springsteen’s birthday. How weird is that?)
(1)SPECjEnterprise2010 result of 36,571.36 on 1 x SPARC T5-8 (8 chips, 128 cores, 3.6 GHz SPARC T5);Oracle WebLogic 12c (12.1.2);Oracle Database 12c (220.127.116.11) vs. IBM result of 10,902.30 on 1 x IBM Power 780(8 chips, 32 cores, 4.42 GHz POWER7+);WebSphere Application Server V8.5;IBM DB2 Universal Database 10.1; Source: http://www.spec.org. Results as of 9/23/13.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
SPEC, SPECint, SPECfp, SPECjbb, SPECweb, SPECjAppServer, SPECjEnterprise, SPECjvm, SPECvirt, SPECompM, SPECompL, SPECsfs, SPECpower, SPEC MPI and SPECpower_ssj are trademarks of the Standard Performance Evaluation Corporation (SPEC).
The postings on this site solely reflect the personal views of the author and do not necessarily represent the views, positions, strategies or opinions of IBM or IBM management.