Solaris 11 outperforms RHEL 6 on 2 socket Intel servers
By user12611852 on Apr 23, 2013
As a long time Sun employee, I've often heard the term "Slow-laris" applied to Oracle's premier Unix operating system. Most frequently this was in comparison to the Linux OS running on small two socket servers. I will admit that in the Solaris 8 and 9 timeframe engineering decisions were made to benefit scalability to 64 sockets that sometimes penalized smaller servers. In addition, because of Solaris long history and derivation from ATT and BSD Unix code, there was undoubtedly a bit of code labeled, "if it ain't broke, don't fix it." With the advent of Solaris 10 and Dynamic Tracing, (DTrace) we actually hunted down and killed a number of those legacy code segments using a new philosophy labeled internally, "If Solaris is slower than Linux on the same hardware, it's a bug."
As a result, Solaris 11 provides higher performance than Red Hat Enterprise Linux 6.3 on basically identical 2 socket hardware as measured by the SPECjbb benchmark. According to SPEC:
The SPECjbb2013 benchmark has been developed from the ground up to measure performance based on the latest Java application features. It is relevant to all audiences who are interested in Java server performance, including JVM vendors, hardware developers, Java application developers, researchers and members of the academic community.
Java is one of the predominant enterprise programming environments for mission critical applications and many of Oracle's products are written in Java.
This chart from the SPECjbb site shows the performance of our X3-2 Intel based server with 16 cores and 128 GB of RAM running Solaris 11.1. The X3-2 tested features the Intel E5-2690 CPU @ 2.9 Ghz.
By comparison, an HP ML350P with the identical Intel chip and clock speed running RHEL 6.3 produces this chart. Clearly, Solaris 11 produce a smoother response curve with higher numbers for both MaxjOPS and Critical jOPS. In addition, the X3-2 system requires only 1 rack unit vs. 4 rack units for the HP model reducing data center requirements.
At the same time, it provides virtualization, security and availability features unavailable on RHEL including:
- Solaris zones
- Network virtualization
- ZFS file system
- Dynamic Tracing
- Predictive self-healing
- Service Management Facility
- Trusted Extensions
- Image packaging system
See more at:
- Jeff Victor's blog
- Oracle's Performance Blog
- SPEC and the benchmark name SPECjbb are registered trademarks of Standard Performance Evaluation Corporation (SPEC). Results as of 4/22/2013, see http://www.spec.org for more information.
- SPARC T5-2 75,658 SPECjbb2013-MultiJVM max-jOPS, 23,334 SPECjbb2013-MultiJVM critical-jOPS. Sun Server X2-4 65,211 SPECjbb2013-MultiJVM max-jOPS, 22,057 SPECjbb2013-MultiJVM critical-jOPS. Sun Server X3-2 41,954 SPECjbb2013-MultiJVM max-jOPS, 13,305 SPECjbb2013-MultiJVM critical-jOPS. SPARC T4-2 34,804 SPECjbb2013-MultiJVM max-jOPS, 10,101 SPECjbb2013-MultiJVM critical-jOPS. HP ProLiant DL560p Gen8 66,007 SPECjbb2013-MultiJVM max-jOPS, 16,577 SPECjbb2013-MultiJVM critical-jOPS. HP ProLiant ML350p Gen8 40,047 SPECjbb2013-MultiJVM max-jOPS, 12,308 SPECjbb2013-MultiJVM critical-jOPS. Supermicro X8DTN+ 20,977 SPECjbb2013-MultiJVM max-jOPS, 6,188 SPECjbb2013-MultiJVM critical-jOPS. HP ProLiant ML310e Gen8 12,315 SPECjbb2013-MultiJVM max-jOPS, 2,908 SPECjbb2013-MultiJVM critical-jOPS. Intel R1304BT 6,198 SPECjbb2013-MultiJVM max-jOPS, 1,722 SPECjbb2013-MultiJVM critical-jOPS.