IBM submitted a new SpecjAppServer2002 benchmark number running WebSphere 5.1 on an eServer xSeries x335, in the multinode category.
- Posted by: Dion Almaer
- Posted on: November 27 2003 11:34 EST
IBM now leads the multinode category in performance with 2,575.34 total operations per second (TOPS) with a fairly low submission on price/performance ($330.07/TOPS).
Application Server: WebSphere 5.1 Application Server, with 2 Intel Xeon DP CPUs at 3200 Mhz
Hardware: eServer xSeries 335 Cluster
JVM: IBM's 1.4.1 JRE
JDBC Driver: IBM DB2 JDBC Universal Driver Provider (Type 2)
OS: SuSE Linux Enterprise Server 8 SP2A with ReiserFS
Database: DB2 Universal Database v126.96.36.199 FP4, Enterprise Server Edition running on AIX
There were 9 application servers systems running, with 1 database.
You can view the details on this result at:
You can view all the results at:
- Hmmm. Looks like HP/BEA still leads in performance... by Sam Pullara on November 27 2003 21:17 EST
- Hmmm. Looks like HP/BEA still leads in performance... by Dario Bassan on December 01 2003 06:45 EST
- SPECJAppServer2002: IBM leads multinode category with new result by Dirk Ludwig on November 28 2003 09:13 EST
...by quite a bit:
HP Integrity Superdome / BEA WebLogic Server 8.1 SP1 on HP-UX 11i v2
HP rp7410 and HP Superdome / BEA WebLogic Server 8.1 on HP-UX 11i
HP J2EE Application Server (7 systems)
# of CPUs: 8
Memory (MB): 32768
IBM J2EE Application Server (9 systems)
# of CPUs: 2
Memory (MB): 3072
HP Database Server (1 system)
# of CPUs: 40
Memory (MB): 40960
IBM Database Server (1 system)
# of CPUs: 8
Memory (MB): 16GB
HP Total System Cost: US$ 4,886,443
IBM Total System Cost: US$ 850,025
Frankly spoken, I don't give damn about any of these benchmarks, since they are absolutely meaningsless (de do do do, de da da da ...) and only serve marketing purposes.
Performance is _VERY_ heavy influenced by the application and not only by the system environment. So, in the end, what does some kind of benchmark tell you? Only that the application tested by the benchmark, using a certain system environment, has <xyz> TOPS. Unfortunately I usually develop a different application (and even more: deploy it on a different system environment).