Technical data

ManualsBrandsFujitsu ManualsComputersPRIMERGY TX150 Torre

White Paper ⏐Performance Report PRIMERGY TX150 S6 Version: 5.1, November 2008

SPECjbb2005

∗

Benchmark description

SPECjbb2005 is a Java business benchmark that focuses on the performance of Java server platforms. It is essentially a

modernized version of SPECjbb2000 with the main differences being:

• The transactions have become more complex in order to cover a greater functional scope.

• The working set of the benchmark has been enlarged to the extent that the total system load has increased.

• SPECjbb2000 allows only one active Java Virtual Machine instance (JVM), whereas SPECjbb2005 permits several

instances, which in turn achieves greater closeness to reality, particularly with large systems.

On the software side SPECjbb2005 measures the implementations of the JVM, JIT (Just-In-Time) compiler, garbage

collection, threads and some aspects of the operating system. As far as hardware is concerned, it measures the effi-

ciency of the CPUs and caches, the memory subsystem and the scalability of shared memory systems (SMP). Disk and

network I/O are irrelevant.

SPECjbb2005 emulates a 3-tier client/server system that is typical for modern business process applications with em-

phasis on the middle tier system:

• Clients generate the load, consisting of driver threads, which on the basis of the TPC-C benchmark generate OLTP

accesses to a database without thinking times.

• The middle-tier system implements the business processes and the updating of the database.

• The database takes on the data management and is emulated by Java objects that are in the memory. Transaction

logging is implemented on an XML basis.

The major advantage of this benchmark is that it includes all three tiers that run together on a single host. The perform-

ance of the middle tier is measured, thus avoiding large-scale hardware installations and making direct comparisons

possible between SPECjbb2005 results of different systems. Client and database emulation are also written in Java.

SPECjbb2005 only needs the operating system as well as a Java Virtual Machine with J2SE 5.0 features.

The scaling unit is a warehouse with approx. 25 MB Java objects. Precisely one Java thread per warehouse executes

the operations on these objects. The business operations are assumed by TPC-C:

• New Order Entry

• Payment

• Order Status Inquiry

• Delivery

• Stock Level Supervision

• Customer Report

However, these are the only features SPECjbb2005 and TPC-C have in common. The results of the two benchmarks are

not comparable.

SPECjbb2005 has 2 performance metrics:

• bops (business operations per second) is the overall rate of all business operations performed per second.

• bops/JVM is the ratio of the first metrics and the number of active JVM instances.

In comparisons of various SPECjbb2005 results it is necessary to state both metrics.

The following rules, according to which a compliant benchmark run has to be performed, are the basis for these metrics:

A compliant benchmark run consists of a sequence of measuring points with an increasing number of warehouses (and

thus of threads) with the number in each case being increased by one warehouse. The run is started at one warehouse

up through 2*MaxWhm but not less than 8 warehouses. MaxWhm is the number of warehouses with the highest opera-

tion rate per second the benchmark expects. Per default the benchmark equates MaxWH with the number of CPUs visi-

ble by the operating system.

The metrics bops is the arithmetic average of all measured operation rates with between MaxWhm warehouses and

2*MaxWhm warehouses.

∗

SPEC®, SPECjbb® and the SPEC logo are registered trademarks of the Standard Performance Evaluation

Corporation (SPEC).