Sun's Hotspot JVM continues to demonstrate industry leading performance. Here's just a few examples where Hotspot shines. SPECjbb2005 Leading x64 on Opteron 2-core result; 27004 bops, 27004 bops/JVM; Sun Fire X4100 and Sun Fire X4200 Leading x64 on Xeon 2-core result; 28,314 bops, 28,314 bops/JVM Fujitsu Siemens Computers PRIMERGY TX300 S2 Leading x64 on Opteron 4-core result: 45,124 bops, 45,124 bops/JVM Sun Fire X4100 and Sun Fire X4200 Best of class 1U result; Sun Fire T1000, 51,540 bops, 12,885 bops/JVM; Results under review. Best of class 2U result; 63,378 bops, 15,845 bops/JVM; Sun Fire T2000, powered by UltraSPARC T1 SPECjappserver2004 SPECjappserver2004 World Record 6 Sun Fire T2000 servers SPECjappserver2004 Single J2EE Node World Record 1 Sun Fire T2000 server SciMark Top 3 submitted results; running Solaris, Linux, and Windows Please post comments and questions here or on the java.net performance forum sharing your experiences running Hotspot. Yes, I'd love to here success stories, but what is most important are those situations where performance wasn't what you expected. We are serious about Java performance here at Sun, and want to do what it takes to make every Java user satisfied with the performance of their application. We want to fix any and all performance issues you run into. We can and will continue to demonstrate industry leading performance, but what is most important is broad and reliable JVM performance which is defined individually with every user's application. Fine print SPEC disclosure: SPECjbb2005 Sun Fire X4200 (2 chips, 2 cores, 2 threads) 27004 bops, 27004 bops/JVM, Fujitsu Siemens Computers PRIMERGY TX300 S2 (2 chips, 2 cores, 4 threads) 28,314 bops, 28,314 bops/JVM, Sun Fire X4200 (2 chips, 4 cores, 4 threads) 45,124 bops, 45,124 bops/JVM, Sun Fire T1000 (1 chip, 8 core, 32 threads) 51,540 bops, 12,885 bops/JVM submitted for review, Sun Fire T2000 (1 chip, 8 core, 32 threads) 63,378 bops, 15,845 bops/JVM. SPEC™ and the benchmark name SPECjbb2005™ are trademarks of the Standard Performance Evaluation Corporation. Competitive benchmark results stated above reflect results published on www.spec.org as of November 30, 2005. For the latest SPECjbb2005 benchmark results, visit http://www.spec.org/osg/jbb2005.

Take a look at the latest SPECappserver2004 World Record results. BEA Weblogic running on Sun Fire T2000 servers powered by UltraSPARC T1 processors and Sun J2SE 5.0_06. Thats right BEA's "Record setting Weblogic 9" set the world records running on Sun's Hotspot JVM. SPECjappserver2004 World Record (Multi-Node) SPECjappserver2004 World Record (2-Node) But how can this be? Sounds like BEA Weblogic relies on the cool performance and reliability of Sun's Hotspot JVM to achieve their world record performance on SPECjappserver2004.

Check out our new Java performance tuning whitepaper on java.sun.com. This has been on the Java performance group's to do list for very long time, thanks to Tom Marble for making this happen. There's nothing liking the kickin' performance the new UltraSPARC T1 processor, the Sun Fire T1000 and T2000 servers, and our latest update release J2SE 5.0_06 to give the needed kick in the pants to put out a tuning guide. This is a work in progress so your feedback is very much appreciated and needed. Thanks.

Sun has announced the new Sun Fire T1000 and T2000 servers today along with SPECjbb2005 benchmark results on these systems. What makes these results so special? They run the UltraSPARC T1 processor with 8 cores and 32 threads on a single chip. The performance of the UltraSPARC T1 systems easily surpasses performance on all other 1U, 2U, or 4U Systems. These results also leverage the high performance features in the newly released J2SE 5.0._06. Take a look at the the chart below. The Sun T2000 surpasses all other competition in the 2U and 4U space. The 1U Sun Fire T1000 leads the 1U results. How are these results comparable? Its simple, compare the raw throughput SPECjbb2005 bops score. One may ask: "How can you compare a 8 core / 32 thread box to a 4 core / 8 thread Power 5+?". Its easy. Chip and core counts are steadily becoming irrelavent. What really matters is how much work (throughput) a system can achieve, how much is that system going to cost to run, and how much lab space, power, and cooling will this system require. Looking at the above results with this in mind clearly shows why Sun UltraSPARC T1 systems are separate from the pack. Sun Fire UltraSPARC T1 much, much less expensive to run than is competitors. How about those Cool Threads! Here's the details on the configurations compared above: How about scalability? Here's a good example of how the Sun Fire T2000 and the UltraSPARC T1 processor scales from 1 to 32 threads. Each SPECjbb2005 is a new thread. Throughput steadily increases as new threads are added, peaking at 32. Fine print SPEC disclosure: SPECjbb2005 Sun Fire T1000 (1 chip, 8 core, 32 threads) 51,540 bops, 12,885 bops/JVM submitted for review, Sun Fire T2000 (1 chip, 8 core, 32 threads) 63,378 bops, 15,845 bops/JVM submitted for review, IBM eServer p5 520 (2 chips, 2 cores, 4 thread) 32,820 bops, 32,820 bops/JVM, AMD Tyan white box (2 chips, 4 cores, 4 thread) 44,574 bops, 44,574 bops/JVM, IBM eServer p5 550 (4 chips, 4 cores, 4 thread) 61,789 bops, 61,789 bops/JVM . SPEC™ and the benchmark name SPECjbb2005™ are trademarks of the Standard Performance Evaluation Corporation. Competitive benchmark results stated above reflect results published on www.spec.org as of November 30, 2005. For the latest SPECjbb2005 benchmark results, visit http://www.spec.org/osg/jbb2005.

[ T: http://technorati.com/tag/NiagaraCMT ]