That got your attention didn’t it?
We’ve announced another performance and benchmark record this week, IBM WebSphere Application Server benchmark involved more than 109,850 concurrent clients and produced 14,004.42 SPECjAppServer2004 JOPS@Standard (jAppServer Operations Per Second), which translates into more than 50 million business transactions over the course of the benchmark’s hour-long runtime. That’s a lot of clients, and a lot of transactions!
The performance run was completed on IBM POWER6 BladeCenter servers powered by two dual-core IBM® POWER6® 4.0 GHz processors and IBM DB2 Universal Database v9.5 on a System p p595 running AIX.
We ran the test over 52-processors, 2-cores per processor and with SMT on. The software config included 26 WAS instances. Now, the issue here isn’t performance, 26-instances isn’t so bad from a config and deployment perspective either. But wouldn’t it be better if you could bundle that all up into a couple of racks and use cloning, automatic deployment, recovery, scheduling etc. and on an even more consolidated, energy efficient platform.
Funnily enough, we are working on that. The IBM Press release mentions IMPACT 2008, that might be good timing, I won’t be there as I’m off to do the Machu Picchu thing at the start of April.
Prior to the new WebSphere+Power double-up, the 4Q2007 record was held by Oracle on HP-UX Integrity Server Blade Cluster, with 10,519.43 JOPS over 24 server instances on 22 2-core processors; Sun also submitted a SPARC T5120 SPECjAppServer2004 benchmark with Sun Java System Application Server 9.1 running 6-nodes, 18-server instances on 48-cores, 6-chips and only scored 8,439.36 JOPS.
You can read the full press release with links to SPEC and IMPACT 2008 here.