SPECjEnterprise2010 Result: WebSphere Application Server V7 on IBM System x HS22 and DB2 9.7 on IBM System x3850 X5

SPECjEnterprise®2010 Result
Copyright © 2009-2010 Standard Performance Evaluation Corporation

WebSphere Application Server V7 on IBM System x HS22 and DB2 9.7 on IBM System x3850 X5

15,829.86 SPECjEnterprise2010 EjOPS

Submitter:
IBM Corporation

SPEC license # 11

Test date:
Aug-2010

Software Products
WebSphere Application Server V7 with Feature Pack for OSGi Applications and Java Persistence API 2.0
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64)
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64)
IBM DB2 Universal JDBC Drivers (3.58.82)
DB2 9.7 FP3

Software Configurations
JEE Application Server
Emulator Software Config
Database Software Config
Driver Config

Hardware Systems
JEE AppServer HW
Database Server HW
Load Driver HW
Emulator HW

System Configuration Diagram

Benchmark
Modifications
Configuration
Bill of Materials
Other Info
General Notes
Full Disclosure Archive

SUT Configuration

JEE Server Nodes:	6	DB Server Nodes:	1
JEE Server CPUs:	72 cores, 12 chips	DB Server CPUs:	32 cores, 4 chips
JEE Instances:	24	DB Instances:	1

Other SUT Components:
4 x 3Com Switch 4200G 48-Port Switches

Benchmark Settings

Dealer Injection Rate:	9,950	Ramp Up Time:	1,200 seconds
DB Load Injection Rate:	10,000	Steady State Time:	3,600 seconds
# of Dealer Agents:	99,500	Ramp Down Time:	600 seconds
# of Manufacturing Agents:	29,850

Detailed Results

Dealer Transaction Mix	Count	Tx. Mix	Failure Count
Purchase	8,999,431	25.01%	6
Manage	8,998,267	25.00%	12
Browse	17,992,391	49.99%	0
Total # Dealer Transactions	35,990,089

Manufacturing Transaction Mix	Count	Tx. Mix	Failure Count
CreateVehicleEJB	10,498,027	50.00%	3,966
CreateVehicleWS	10,499,384	50.00%	3,777
Total # Manufacturing Transactions	20,997,411

Response Times	Average	Standard Deviation	Maximum	90th%	Reqd
Purchase	0.253	0.00	18.175	0.490	2.000
Manage	0.172	0.00	13.979	0.370	2.000
Browse	0.286	3.77	14.945	0.550	2.000
CreateVehicleEJB	0.151	0.00	10.806	0.240	5.000
CreateVehicleWS	0.261	0.00	11.417	0.490	5.000

Reproducibility Run (SPECjEnterprise2010 EjOPS)	15,831.39

WebSphere Application Server V7 with Feature Pack for OSGi Applications and Java Persistence API 2.0

Vendor:	IBM Corporation	Availability:	Jun-2010
CTS Version:	5.0	Date Passed CTS:	Apr-2010
OS Name:	Novell SUSE Linux Enterprise Server 10 SP3
EJB Protocol:	RMI/IIOP

IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64)

Vendor:	IBM Corporation	Availability:	Jun-2010
OS Name:	Novell SUSE Linux Enterprise Server 10 SP3

IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64)

Vendor:	IBM Corporation	Availability:	Mar-2010
OS Name:	Novell SUSE Linux Enterprise Server 10 SP2

IBM DB2 Universal JDBC Drivers (3.58.82)

Vendor:	IBM Corporation	Availability:	Nov-2009
OS Name:	Novell SUSE Linux Enterprise Server 10 SP2

DB2 9.7 FP3

Vendor:	IBM Corporation	Availability:	Nov-2009
OS Name:	Novell SUSE Linux Enterprise Server 10 SP2

JEE Application Server

JEE Product:	WebSphere Application Server V7 with Feature Pack for OSGi Applications and Java Persistence API 2.0
JVM Product:	IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64)
JDBC Product:	IBM DB2 Universal JDBC Drivers (3.58.82)
Hardware:	JEE AppServer HW
# of Instances:	24
Interfaces:
	Web Interface for the Order Domain
	Web Services Interface for the Supplier Domain
	EJB Interface for the Manufacturing Domain
	Web Services Interface for the Manufacturing Domain

Notes / Tuning Information

JVM Parameters:
-Xms3072m -Xmx3072m -Xss128k -Xgcpolicy:gencon -Xnoloa -Xmo756m -Xmn2316m -Xtrace:none -Xlp -Xcompressedrefs
-Xgcthreads6 -Xdisableexplicitgc -Dcom.ibm.CORBA.FragmentSize=10000 -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
-Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=0
Refer to files appservers/node.resources.xml, and appservers/server.xml
for all server configuration and resource configuration
information

Emulator Software Config

JEE Product:	WebSphere Application Server V7 with Feature Pack for OSGi Applications and Java Persistence API 2.0
JVM Product:	IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64)
Hardware:	Emulator HW
# of Instances:	12

Notes / Tuning Information

JVM Parameters:
-Xms2048m -Xmx2048m -Xss128k -Xgcpolicy:gencon -Xnoloa -Xmo512m -Xmn1536m -Xtrace:none -Xlp -DdisableWSAddressCaching=true
-Xgcthreads8 -Xdisableexplicitgc -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
-Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=0
Refer to files emulator/server.xml
for all server configuration and resource configuration
information

Database Software Config

DB Product:	DB2 9.7 FP3
Hardware:	Database Server HW
# of Instances:	1
Character Set:	UTF-8

Notes / Tuning Information

DB2_USE_ALTERNATE_PAGE_CLEANING=ON
DB2_APM_PERFORMANCE=ON
DB2_KEEPTABLELOCK=CONNECTION
DB2COMM=TCPIP
DB2_MINIMIZE_LISTPREFETCH=YES
DFT_MON_BUFPOOL on
DFT_MON_LOCK off
DFT_MON_SORT off
DFT_MON_STMT off
DFT_MON_TIMESTAMP on
DFT_MON_UOW on
DFT_MON_TABLE off
HEALTH_MON off
CPUSPEED -1
SVCENAME 60004
LOGBUFSZ 4096
LOGPRIMARY 52
LOGSECOND 0
SOFTMAX 3000
CHNGPGS_THRESH 99
LOGFILSIZ 65535
NEWLOGPATH /dev/speclogs/speclogLV
AUTO_MAINT off
AUTO_RUNSTATS off
AUTO_TBL_MAINT off
NUM_IOCLEANERS 128
LOCKLIST 100000
MAXLOCKS 100
MINCOMMIT 1
MON_REQ_METRICS none
MON_ACT_METRICS none
MON_OBJ_METRICS none
AUTO_STMT_STATS off
IBMDEFAULTBP immediate size 19100000
INDEX_BP immediate size 9130000
JMS_BP immediate size 2710
M_INV_BP immediate size 202694
M_PARTS_BP immediate size 100352
M_BOM_BP immediate size 25791
M_WO_BP immediate size 30000
O_ORDERS_BP immediate size 481587
O_ORDERS2_BP immediate size 321058
O_OL_BP immediate size 481587
O_CI_BP immediate size 2584559
O_CUSTOMER_BP immediate size 1583569
O_ITEM_BP immediate size 3050
O_ITEM2_BP immediate size 1000
S_COMPONENT_BP immediate size 481586
S_S_C_BP immediate size 321058
S_P_O_BP immediate size 722380
S_P_OL_BP immediate size 142693
DATA_BP immediate size 13000000
O_ORDERLINE append on
O_CUSTINVENTORY append on
O_ORDERS append on
S_PURCH_ORDER append on
S_PURCH_ORDERLINE append on
M_WORKORDER append on
M_WORKORDER volatile
O_ITEM volatile
M_PARTS volatile
M_INVENTORY volatile

Driver Config

JVM Product:	IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64)
Hardware:	Load Driver HW
# of Instances:	25

Notes / Tuning Information

-server -Xms4096M -Xmx4096M -Djava.net.preferIPv4Stack=true
-Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0
-Dcom.ibm.websphere.naming.hostname.normalizer=...none... -DdisableWSAddressCaching=true -Dcom.ibm.CORBA.ConnectionMultiplicity=40

JEE AppServer HW (SUT hardware)

Hardware Vendor:	IBM Corporation	OS Vendor:	Novell
Model Name:	IBM System x HS22	OS Name:	Novell SUSE Linux Enterprise Server 10 SP3
Processor:	Intel Xeon X5670 (Intel Turbo Boost Technology up to 3.33GHz)	Filesystem:	ext3
MHz:	2933	Disks:	1x146GB 10K SAS
# of CPUs:	12 cores, 2 chips, 6 cores/chip (12 HW threads/chip)	Network Interface:	(4) 1000BaseT Ethernet
Memory (MB):	24576	Other Hardware:
DIMM[0] Count:	6	DIMM[0] Size:	4096
L1 Cache:	32 KB I + 32 KB D on chip per core	# of Systems:	6
L2 Cache:	256 KB I+D on chip per core	H/W Available:	Mar-2010
Other Cache:	12 MB I+D on chip per chip	OS Available:	May-2009

Notes / Tuning Information

fs.file-max = 1048576
kernel.sem = 250 32000 100 128
kernel.shmall = 4294967296
kernel.shmmax = 68719476736
net.core.netdev_max_backlog = 400000
net.core.optmem_max = 30000000
net.core.rmem_default = 30000000
net.core.wmem_default = 30000000
net.core.rmem_max = 30000000
net.core.wmem_max = 30000000
net.core.somaxconn = 300000
net.ipv4.conf.all.arp_announce = 2
net.ipv4.conf.all.arp_ignore = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.ip_forward = 0
net.ipv4.ip_local_port_range = 1024 65000
net.ipv4.tcp_fin_timeout = 10
net.ipv4.tcp_max_syn_backlog = 30000
net.ipv4.tcp_max_tw_buckets = 2000000
net.ipv4.tcp_mem  = 30000000 30000000 30000000
net.ipv4.tcp_rmem = 30000000 30000000 30000000
net.ipv4.tcp_wmem = 30000000 30000000 30000000
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_sack = 0
ulimit -n 1048576
vm.nr_hugepages = 6656
nohpet nopmtimer

Database Server HW (SUT hardware)

Hardware Vendor:	IBM Corporation	OS Vendor:	Novell
Model Name:	IBM System x3850 X5	OS Name:	Novell SUSE Linux Enterprise Server 10 SP3
Processor:	Intel Xeon X7560 (Intel Turbo Boost Technology)	Filesystem:	ext3
MHz:	2270	Disks:	2x146Gb 10K 2.5" Hot-Swap SAS HDD
# of CPUs:	32 cores, 4 chips, 8 cores/chip	Network Interface:	(4) 1000BaseT Ethernet
Memory (MB):	393216	Other Hardware:	2xDS4800 Disk System, 12xDS4000 EXP810 Expansion Disk Arrays, 96x73.4GB 15K E-DDM Disks, 96x36.4GB 15K E-DDM Disks
DIMM[0] Count:	24	DIMM[0] Size:	16384
L1 Cache:	32 KB I + 32 KB D on chip per core	# of Systems:	1
L2 Cache:	256 KB I+D on chip per core	H/W Available:	Mar-2010
Other Cache:	24 MB I+D on chip per chip	OS Available:	May-2009

Notes / Tuning Information

fs.file-max = 1048576
kernel.sem = 4096 512000 1600 9000
kernel.shmall = 4294967296
kernel.msgmnb = 524288
net.core.netdev_max_backlog = 400000
net.core.optmem_max = 30000000
net.core.rmem_default = 30000000
net.core.wmem_default = 30000000
net.core.rmem_max = 30000000
net.core.wmem_max = 30000000
net.core.somaxconn = 300000
net.ipv4.conf.all.arp_announce = 2
net.ipv4.conf.all.arp_ignore = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.ip_forward = 0
net.ipv4.ip_local_port_range = 1024 65000
net.ipv4.tcp_fin_timeout = 10
net.ipv4.tcp_max_syn_backlog = 30000
net.ipv4.tcp_max_tw_buckets = 2000000
net.ipv4.tcp_mem  = 30000000 30000000 30000000
net.ipv4.tcp_rmem = 30000000 30000000 30000000
net.ipv4.tcp_wmem = 30000000 30000000 30000000
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_sack = 0
ulimit -n 1048576
nohpet nopmtimer

Load Driver HW (non-SUT hardware)

Hardware Vendor:	IBM Corporation	OS Vendor:	Red Hat
Model Name:	IBM BladeCenter HS21	OS Name:	Red Hat Enterprise Linux 5.2
Processor:	Quad Core Intel(R) Xeon(R) X5470	Filesystem:	Reiser
MHz:	3333	Disks:	1 x 73.4GB SAS 15K rpm
# of CPUs:	8 cores, 2 chips, 4 cores/chip	Network Interface:	(2) 1000BaseT
Memory (MB):	16384	Other Hardware:
L1 Cache:	32KB(I)+32KB(D)	# of Systems:	25
L2 Cache:	2x6MB per chip	H/W Available:	Nov-2008
Other Cache:		OS Available:	Oct-2008

Notes / Tuning Information

fs.file-max = 1048576
kernel.sem = 250 32000 100 128
kernel.shmall = 4294967296
net.core.netdev_max_backlog = 400000
net.core.optmem_max = 30000000
net.core.rmem_default = 30000000
net.core.wmem_default = 30000000
net.core.rmem_max = 30000000
net.core.wmem_max = 30000000
net.core.somaxconn = 300000
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.ip_forward = 0
net.ipv4.ip_local_port_range = 1024 65000
net.ipv4.tcp_fin_timeout = 10
net.ipv4.tcp_max_syn_backlog = 30000
net.ipv4.tcp_max_tw_buckets = 2000000
net.ipv4.tcp_mem  = 30000000 30000000 30000000
net.ipv4.tcp_rmem = 30000000 30000000 30000000
net.ipv4.tcp_wmem = 30000000 30000000 30000000
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_sack = 0
net.ipv4.conf.all.arp_announce = 2
net.ipv4.conf.all.arp_ignore = 1
ulimit -n 1048576

Emulator HW (non-SUT hardware)

Hardware Vendor:	IBM Corporation	OS Vendor:	Novell
Model Name:	IBM BladeCenter HS21	OS Name:	Novell SUSE Linux Enterprise Server 10 SP2
Processor:	Quad Core Intel(R) Xeon(R) X5470	Filesystem:	Reiser
MHz:	3333	Disks:	1 x 73.4GB SAS 15K rpm
# of CPUs:	8 cores, 2 chips, 4 cores/chip	Network Interface:	(4) 1000BaseT
Memory (MB):	16384	Other Hardware:
L1 Cache:	32KB(I)+32KB(D)	# of Systems:	3
L2 Cache:	2x6MB per chip	H/W Available:	Nov-2008
Other Cache:		OS Available:	Oct-2008

Notes / Tuning Information

fs.file-max = 1048576
kernel.sem = 250 32000 100 128
kernel.shmall = 4294967296
kernel.shmmax = 68719476736
net.core.netdev_max_backlog = 400000
net.core.optmem_max = 30000000
net.core.rmem_default = 30000000
net.core.wmem_default = 30000000
net.core.rmem_max = 30000000
net.core.wmem_max = 30000000
net.core.somaxconn = 300000
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.ip_forward = 0
net.ipv4.ip_local_port_range = 1024 65000
net.ipv4.tcp_fin_timeout = 10
net.ipv4.tcp_max_syn_backlog = 30000
net.ipv4.tcp_max_tw_buckets = 2000000
net.ipv4.tcp_mem  = 30000000 30000000 30000000
net.ipv4.tcp_rmem = 30000000 30000000 30000000
net.ipv4.tcp_wmem = 30000000 30000000 30000000
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_sack = 0
net.ipv4.conf.all.arp_announce = 2
net.ipv4.conf.all.arp_ignore = 1
ulimit -n 1048576

Benchmark Modifications
Schema Modifications: Modifications to the schema where made to enable range partitioning. The DDL for creating the range partion tables that were used is included in the FDA under the schema/range_part.ddl
Load Program Modifications: No modifications to the load programs were made.

Benchmark Modifications

Schema Modifications:

  Modifications to the schema where made to enable range partitioning.
  The DDL for creating the range partion tables that were used is
  included in the FDA under the schema/range_part.ddl

Load Program Modifications:

  No modifications to the load programs were made.

Benchmark Configuration Information

Isolation Requirement Info:

  The benchmark meets the isolation level requirements by version column
    checking on entities against the database.
  The ItemEnt bean was cached for 20 minute intervals using
    the WebSphere JPA Object Cache mechanism.

Durability Requirement Info:

  To ensure database durability, RAID10 was used for the
    database logs maintained on the external storage.
    A total of 16 x 73GB disks were used for the log.

Storage Requirement Info:

  Over the course of a 85 minute run at an injection rate of
    9950, the database storage for database system increased by
    12 GB.  Given a linear scale, a 24 hour run at the same
    injection rate would increase storage for database system
    by 204 GB.  One RAID10 disk arrays were used to create the
    filesystem space for the database.  The array contained
    96 x 36GB disks providing 3456 Gb GB of storage.

Bill of Materials

Supplier  Description                                   Product #          Qty
--------  -------------------------------------------   ----------------   ---
IBM       IBM System x3850 X5                           71455RX              1
-          4xIntel Xeon Processor X7560 8C
-            (2.26GHz 24MB L3 Cache 1333MHz 133w)
-          384GB RAM (24x16GB DIMMS), 2x146GB 10k SAS HDD
IBM       DS4800 Disk System Model 82 (4 GB Cache)      1815-82A             2
IBM       DS4000 EXP810 Expansion Unit Model 81         1812-81A            12
IBM       4 Gbps FC, 73.4 GB/15K E-DDM                  5433                96
IBM       4 Gbps FC, 36.4 GB/15K E-DDM                  5433                96
IBM       3 Year Onsite Repair 24x7 4 Hour Response     6756001              1
IBM       SUSE Linux Enterprise Server w/ 3yr support   5639S1X              1
...
IBM       IBM System x HS22                             7870H4X              6
-          2xIntel Xeon Processor X5670 6C
-            (2.93GHz 12MB L3 Cache 1333MHz 95w)
-          24GB RAM (6x4GB DIMMS), 1x146GB 10k SAS HDD
IBM       3 Year Onsite Repair 24x7 4 Hour Response     6756025
IBM       SUSE Linux Enterprise Server w/ 3yr support   5639S1X              6
IBM       IBM BladeCenter H                             88524SU              1
IBM       3 Year Onsite Repair 24x7 4 Hour Response     40Y5981              1
...
CDW       3Com Switch 4200G 48-Port                     1020899              4
CDW       10GBASE-CX4 XENPAK Infiniband 4x Module       3CXENPAK95           6
CDW       3Com Switch 4200G 48-Port Sup 1 yr, 24x7x4    819638              12
...
IBM       DB2 Enterprise Server Edition 9.7             D597RLL            16*
-           Lic+SW Maint 12 Months
IBM       DB2 Enterprise Server Edition 9.7             E00BILL             32
-           SW Maint Rewl 1 Anniv
IBM       WebSphere Application Server V7               D55W8LL           72**
-           Lic+SW Maint 12 Months
IBM       WebSphere Application Server V7               E1CBBLL            144
-           SW Maint Rewl 1 Anniv
-           Fix Pack 9 (7.0.0.9)
-           PM20973
-           Feature Pack for OSGi Applications and Java Persistence API 2.0
...
* Note:  Pricing for DB2 is based on Value Units (VU).  Each Intel core is 70 VU.
** Note:  Pricing for WebSphere is based on Value Units (VU).  Each Intel core is 70 VU.

Other Benchmark Information
DNS round robin load balancing was used and hosted on the database machine All network connections were 1Gbps

General Notes

All exceptions in driver logs are from Optimistic Concurrency Checking.
These exceptions are expected in the benchmark.

The IBM DB2 Universal JDBC Drivers is a type 4 driver.

DB2 uses "Soft" checkpoint to ensure that no updates remain unflushed for
longer than the allowed time.

When DB2 UDB Server changes a database table with an update, insert, or delete
operation, the change is initially made in memory, not on disk. When there is
not enough space in the memory buffer to read in or write additional data pages,
DB2 UDB Server will make space by flushing some modified pages to disk.
Modified pages are also written to disk as part of the "Soft" checkpoint to
ensure that no updates remain unflushed for longer than the allowed time.
Before a change is made to the database, it is first recorded in the
transaction log. This ensures that the database can be recovered completely
in the event of a failure. Using the transaction log, transactions that
started but did not complete prior to a failure can be undone, and
transactions recorded as complete in the transaction log but not yet written
to disk can be redone.

DB2 UDB uses a write-ahead-logging protocol to guarantee recovery. This
protocol uses "Soft" checkpoint to write least-recently-used database pages
to disk independent of transaction commit. However, enough log information to
redo/undo the change to a database pages is committed to disk before the
database page itself is written. This protocol therefore renders checkpoint
unnecessary for DB2 UDB. For a more detailed description of the general
principles of the write-ahead-logging protocol, see the IBM research paper,
ARIES: A Transaction Recovery Method Supporting Fine Granularity Locking and
Partial Rollbacks Using Write-Ahead Logging," by C. Mohan, Database Technology
Institute, IBM Almaden Research Center. (http:// portal.acm.org/citation.cfm
?id=128770&coll=portal&dl=ACM&CFID=10343790&CFTOKEN=42047146)

For questions about this result, please contact the submitter: IBM Corporation
For other inquiries, please contact webmaster@spec.org

Benchmark run on Tue Aug 17 22:38:07 CDT 2010 by SPECjEnterprise20101.0
Result submitted on null
Report generated by SPECjEnterprise2010 Reporter v1.00

First published at SPEC.org on 08-Sep-2010