SPECjAppServer2004 Result: IBM WebSphere Application Server 6.1 with DB2 8.2 on Sun Fire T2000 using Solaris 10

SPECjAppServer®2004 Result
Copyright © 2004 Standard Performance Evaluation Corporation

IBM WebSphere Application Server 6.1 with DB2 8.2 on Sun Fire T2000 using Solaris 10

616.22 SPECjAppServer2004 JOPS@Standard

Submitter:
Sun Microsystems Inc.

SPEC license # 6

Test date:
Jul-2006

Software Products
WebSphere Application Server Network Deployment, Version 6.1
WebSphere Application Server Network Deployment, Version 6.0.2
Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit(IBM build 1.5.0_06-erdist-20060404 20060511)
Java (TM) 2 Platform Standard Edition Development Kit 1.4.2 Update 8 32-bit(IBM build 1.4.2_08-b03 20050517)
IBM DB2 Universal JDBC Drivers
IBM DB2 Universal Database v8.2.4 (64-bit)

Software Configurations
J2EE Application Servers
Emulator SW Config
Database SW Config
Driver SW Config Primary
Driver SW Config Satellite #1

Hardware Systems
J2EE AppServer HW
Database Server HW
Load Driver Master/Satellite HW
Emulator HW

System Configuration Diagram

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

SUT Configuration

J2EE Server Nodes:	1	DB Server Nodes:	1
J2EE Server CPUs:	8 cores, 1 chip	DB Server CPUs:	4 cores, 2 chips
J2EE Instances:	1	DB Instances:	1

Other SUT Components:

Benchmark Settings

Dealer Injection Rate:	372	Ramp Up Time:	600 seconds
# of Dealer Agents:	8	Ramp Down Time:	300 seconds
# of Manufacturing Agents:	4	Steady State Time:	3,600 seconds
DB Load Injection Rate:	400	Trigger Time:	550 seconds

Detailed Results

Dealer Transaction Mix	Count	Tx. Mix
Purchase	333,455	25.01%
Manage	333,064	24.98%
Browse	666,547	50.00%
Total # Dealer Transactions	1,333,066

Total # Manufacturing Transactions	885,341

Response Times	Average	Maximum	90th%	Reqd
Purchase	0.59	17.49	1.20	2.00
Manage	0.44	17.99	1.00	2.00
Browse	0.72	13.90	1.60	2.00
Manufacturing	2.37	11.05	3.50	5.00

Reproducibility Run (SPECjAppServer2004 JOPS)	617.83

WebSphere Application Server Network Deployment, Version 6.1

Vendor:	IBM Corporation	Availability:	Apr-2006
CTS Version:	1.4	Date Passed CTS:	Nov-2004
OS Name:	Solaris 10 6/06 (64-bit)
EJB Protocol:	RMI/IIOP

WebSphere Application Server Network Deployment, Version 6.0.2

Vendor:	IBM Corporation	Availability:	Oct-2005
CTS Version:	1.4	Date Passed CTS:	Nov-2004
OS Name:	Solaris 10 HW2
EJB Protocol:	RMI/IIOP

Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit(IBM build 1.5.0_06-erdist-20060404 20060511)

Vendor:	Sun Microsystems, Inc.	Availability:	Jun-2006
OS Name:	Solaris 10 6/06 (64-bit)

Java (TM) 2 Platform Standard Edition Development Kit 1.4.2 Update 8 32-bit(IBM build 1.4.2_08-b03 20050517)

Vendor:	Sun Microsystems, Inc.	Availability:	Jun-2005
OS Name:	Solaris 10 HW2

IBM DB2 Universal JDBC Drivers

Vendor:	IBM Corporation	Availability:	Jun-2006
OS Name:	Solaris 10 6/06 (64-bit)

IBM DB2 Universal Database v8.2.4 (64-bit)

Vendor:	IBM Corporation	Availability:	Apr-2006
OS Name:	Solaris 10 1/06 (64-bit)

J2EE Application Servers

J2EE Product:	WebSphere Application Server Network Deployment, Version 6.1
JVM Product:	Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit(IBM build 1.5.0_06-erdist-20060404 20060511)
JDBC Product:	IBM DB2 Universal JDBC Drivers
Hardware:	J2EE AppServer HW
# of Instances:	1
Interfaces:
	Web Interface for the Dealer Domain
	Web Interface for the Supplier Domain
	EJB Interface for the Dealer Domain
	EJB Interface for the Manufacturing Domain
	EJB Interface for the Supplier Domain

Notes / Tuning Information

JVM Options: Minimum heap size=2880 MB Maximum heap size=2880 MB
initialHeapSize="2880" maximumHeapSize="2880" verboseModeGarbageCollection="true
-server -Xmn780m -Xss128k -XX:-ScavengeBeforeFullGC -XX:+UseParallelGC
-XX:ParallelGCThreads=24 -XX:PermSize=128m -XX:MaxTenuringThreshold=16
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+UseParallelOldGC
-Dcom.ibm.ws.pm.batch=true -Dcom.ibm.ws.pm.deferredcreate=true
-Dcom.ibm.CORBA.FragmentSize=3000 -Dcom.ibm.ws.pm.useLegacyCache=false
-Dcom.ibm.ws.pm.grouppartialupdate=true
-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
-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XML11Configuration
 EJB Cache Size = 37543
 HTTP Channel maximum persistent requests = -1
 HTTP Channel readTimeout/writeTimeout = 6000/6000
 HTTP Channel persistentTimeout = 3000
 Web Container threads (Minumum/Maximum) = 56/56
 ORB threads (Minumum/Maximum) = 40/40
 Default threads (Minumum/Maximum) = 15/15
Java process changed to run in FX class using:
 /usr/bin/priocntl -s -c FX -m 59 -p 59 -i pid 
For other configuration items refer to Config/AppServers/*.xml files.

Emulator SW Config

J2EE Product:	WebSphere Application Server Network Deployment, Version 6.0.2
JVM Product:	Java (TM) 2 Platform Standard Edition Development Kit 1.4.2 Update 8 32-bit(IBM build 1.4.2_08-b03 20050517)
Hardware:	Load Driver Master/Satellite HW
# of Instances:	1

Notes / Tuning Information

JVM Options: -server initialHeapSize="2560" maximumHeapSize="2560" -Xmn800m
-Xss128k -XX:-UseAdaptiveSizePolicy -XX:+DisableExplicitGC -Xmn1536m
verboseModeGarbageCollection="true" -XX:+PrintGCDetails -XX:+PrintGCTimeStamps
-XX:MaxPermSize=256m -XX:MaxTenuringThreshold=3 -XX:+UseParallelGC
-XX:ParallelGCThreads=16

Database SW Config

DB Product:	IBM DB2 Universal Database v8.2.4 (64-bit)
Hardware:	Database Server HW
# of Instances:	1

Notes / Tuning Information

Tuning performed by db2tune.sh script in the archive/Schema directory for the first
time after db creation. Then before each run db was loaded using the archive
created and then tuning was done using tun2.sh.

Driver SW Config Primary

JVM Product:	Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit(IBM build 1.5.0_06-erdist-20060404 20060511)
Hardware:	Load Driver Master/Satellite HW
# of Instances:	1

Notes / Tuning Information

JVM Options: -server -Xms600m -Xmx600m -XX:+UseMPSS
-XX:-UseAdaptiveSizePolicy -XX:+UseParallelGC -XX:MaxTenuringThreshold=3
-XX:SurvivorRatio=2 -Xss128k -Dcom.ibm.CORBA.FragmentSize=3000
-Dsun.rmi.dgc.client.gcInterval=4200000 -Dsun.rmi.dgc.server.gcInterval=4200000
-Dorg.omg.CORBA.ORBInitialHost=${JAS_HOST}
-Djava.naming.factory.initial=${JNDI_CLASS} -Djava.naming.provider.url=${NAMING_PROVIDER}
-Djava.ext.dirs=${J2EE_HOME}/classes:${JAVA_HOME}/jre/lib/ext:${J2EE_HOME}/lib

Driver SW Config Satellite #1

JVM Product:	Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit(IBM build 1.5.0_06-erdist-20060404 20060511)
Hardware:	Load Driver Master/Satellite HW
# of Instances:	1

Notes / Tuning Information

JVM Options: -server -Xms600m -Xmx600m -XX:+UseMPSS
-XX:-UseAdaptiveSizePolicy -XX:+UseParallelGC -XX:MaxTenuringThreshold=3
-XX:SurvivorRatio=2 -Xss128k -Dcom.ibm.CORBA.FragmentSize=3000
-Dsun.rmi.dgc.client.gcInterval=4200000 -Dsun.rmi.dgc.server.gcInterval=4200000
-Dorg.omg.CORBA.ORBInitialHost=${JAS_HOST} -Djava.naming.factory.initial=${JNDI_CLASS}
-Djava.ext.dirs=${J2EE_HOME}/classes:${JAVA_HOME}/jre/lib/ext:${J2EE_HOME}/lib

J2EE AppServer HW (SUT hardware)

Hardware Vendor:	Sun Microsystems, Inc.	OS Vendor:	Sun Microsystems, Inc.
Model Name:	Sun Fire T2000	OS Name:	Solaris 10 6/06 (64-bit)
Processor:	Sun UltraSPARC T1	Filesystem:	UFS
MHz:	1200	Disks:	2x73Gb 10K RPM SAS
# of CPUs:	8 cores, 1 chip, 8 cores/chip (4 threads/core)	Network Interface:	(4) 1000 BaseT Ethernet
Memory (MB):	32760	Other Hardware:
L1 Cache:	16KB(I)+8KB(D) per core	# of Systems:	1
L2 Cache:	3MB per chip	H/W Available:	Nov-2005
Other Cache:		OS Available:	Jun-2006

Notes / Tuning Information

One application server instance used for this benchmark.

System Tuning:
set segkmem_lpsize=0x400000
set rlim_fd_max=260000
set autoup=900
set tune_t_fsflushr=1
set sq_max_size=0
set ipge:ipge_tx_ring_size=2048
set ipge:ipge_reclaim_pending=32
set ipge:ipge_bcopy_thresh = 512
set ipge:ipge_dvma_thresh = 1
set ip:ip_squeue_fanout=1
set ip:ip_squeue_bind=0
set ipge:ipge_tx_syncq=1
set ipge:ipge_srv_fifo_depth=2048
set consistent_coloring=2
Network Tuning:
ndd -set /dev/tcp tcp_conn_req_max_q 16384
ndd -set /dev/tcp tcp_conn_req_max_q0 16384
ndd -set /dev/tcp tcp_xmit_hiwat 400000
ndd -set /dev/tcp tcp_recv_hiwat 400000
ndd -set /dev/tcp tcp_cwnd_max 2097152
ndd -set /dev/tcp tcp_ip_abort_interval 60000
ndd -set /dev/tcp tcp_rexmit_interval_initial 4000
ndd -set /dev/tcp tcp_rexmit_interval_max 10000
ndd -set /dev/tcp tcp_rexmit_interval_min 3000
ndd -set /dev/tcp tcp_max_buf 4194304

Database Server HW (SUT hardware)

Hardware Vendor:	Sun Microsystems, Inc.	OS Vendor:	Sun Microsystems, Inc.
Model Name:	Sun Fire X4200	OS Name:	Solaris 10 1/06 (64-bit)
Processor:	Dual Core AMD Opteron(tm) Processor 275	Filesystem:	UFS
MHz:	2200	Disks:	2x73Gb 10K RPM SAS
# of CPUs:	4 cores, 2 chips, 2 cores/chip	Network Interface:	(1) 1000 BaseT Ethernet
Memory (MB):	16256	Other Hardware:	2x Sun SE3320 Array (12x 73GB 10K RPM SCSI Disk Array)
L1 Cache:	64KB(I)+64KB(D) per core	# of Systems:	1
L2 Cache:	1MB	H/W Available:	Aug-2005
Other Cache:		OS Available:	Jan-2006

Notes / Tuning Information

X4200 comes with 4GB(4X1GBDIMM) which was taken out and 16GB(8X2GB DIMM's) were put in.
System Tuning /etc/system:
set maxusers=1024
set msgsys:msginfo_msgmni = 2560
set semsys:seminfo_semmni = 3072
set shmsys:shminfo_shmmax = 15392386252
set shmsys:shminfo_shmmni = 3072


UFS options for database files: forcedirectio
Network Tuning:
ndd -set /dev/tcp tcp_conn_req_max_q 16384
ndd -set /dev/tcp tcp_conn_req_max_q0 16384
ndd -set /dev/tcp tcp_xmit_hiwat 400000
ndd -set /dev/tcp tcp_recv_hiwat 400000
ndd -set /dev/tcp tcp_cwnd_max 2097152
ndd -set /dev/tcp tcp_ip_abort_interval 60000
ndd -set /dev/tcp tcp_rexmit_interval_initial 4000
ndd -set /dev/tcp tcp_rexmit_interval_max 10000
ndd -set /dev/tcp tcp_rexmit_interval_min 3000
ndd -set /dev/tcp tcp_max_buf 4194304

Load Driver Master/Satellite HW (non-SUT hardware)

Hardware Vendor:	Sun Microsystems, Inc.	OS Vendor:	Sun Microsystems, Inc.
Model Name:	Sun Java WorkStation W2100Z	OS Name:	Solaris 10 HW2
Processor:	AMD Opteron(tm) Processor 250	Filesystem:	UFS
MHz:	2393	Disks:	1 x 73GB Internal Disk
# of CPUs:	2 cores, 2 chips, 1 core/chip	Network Interface:	(1) Onboard 1000BaseT Ethernet
Memory (MB):	7423	Other Hardware:
L1 Cache:	64KB(I)+64KB(D) per core	# of Systems:	2
L2 Cache:	1MB	H/W Available:	Jul-2004
Other Cache:		OS Available:	Nov-2005

Notes / Tuning Information

System Tuning:

Network Tuning:
ndd -set /dev/tcp tcp_conn_req_max_q 16384
ndd -set /dev/tcp tcp_conn_req_max_q0 16384
ndd -set /dev/tcp tcp_xmit_hiwat 400000
ndd -set /dev/tcp tcp_recv_hiwat 400000
ndd -set /dev/tcp tcp_cwnd_max 2097152
ndd -set /dev/tcp tcp_ip_abort_interval 60000
ndd -set /dev/tcp tcp_rexmit_interval_initial 4000
ndd -set /dev/tcp tcp_rexmit_interval_max 10000
ndd -set /dev/tcp tcp_rexmit_interval_min 3000
ndd -set /dev/tcp tcp_max_buf 4194304

Emulator HW (non-SUT hardware)

Hardware Vendor:	Sun Microsystems, Inc.	OS Vendor:	Sun Microsystems, Inc.
Model Name:	Sun Fire T2000	OS Name:	Solaris 10 HW2
Processor:	Sun UltraSPARC T1	Filesystem:	UFS
MHz:	1000	Disks:	2 x 73Gb FC
# of CPUs:	8 cores, 1 chip, 8 cores/chip (4 threads/core)	Network Interface:	(4) Onboard 1000BaseT Ethernet
Memory (MB):	16376	Other Hardware:
L1 Cache:	16KB(I)+8KB(D) per core	# of Systems:	1
L2 Cache:	3MB per Chip	H/W Available:	Nov-2005
Other Cache:		OS Available:	Nov-2005

Notes / Tuning Information

System Tuning in /etc/system:
set rlim_fd_max=260000
set autoup=900
set tune_t_fsflushr=1
set sq_max_size=0
set ipge:ipge_tx_ring_size=2048
set ipge:ipge_srv_fifo_depth=16000
set ipge:ipge_reclaim_pending=32
set ipge:ipge_bcopy_thresh = 512
set ipge:ipge_dvma_thresh = 1
set ip:ip_squeue_fanout=1
Network Tuning:
ndd -set /dev/tcp tcp_conn_req_max_q 16384
ndd -set /dev/tcp tcp_conn_req_max_q0 16384
ndd -set /dev/tcp tcp_xmit_hiwat 400000
ndd -set /dev/tcp tcp_recv_hiwat 400000
ndd -set /dev/tcp tcp_cwnd_max 2097152
ndd -set /dev/tcp tcp_ip_abort_interval 60000
ndd -set /dev/tcp tcp_rexmit_interval_initial 4000
ndd -set /dev/tcp tcp_rexmit_interval_max 10000
ndd -set /dev/tcp tcp_rexmit_interval_min 3000
ndd -set /dev/tcp tcp_max_buf 4194304

Benchmark Modifications
Schema Modifications: Scripts to create the DB are included in the FDA.
Load Program Modifications: The load program was not modified

Benchmark Configuration Information
Isolation Requirement Info: The following beans: PartEnt, ComponentEnt, AssemblyEnt, BomEnt and LargeOrderEnt in the Manufacturing Domain, ItemEnt in the Orders Domain, and SupplierCompEnt and SupplierEnt in the Supplier Domain were accessed using READ_COMMITTED which is Cursor Stability (CS) for DB2. The remaining beans were accessed using REPEATABLE_READ which translates to DB2 isolation level of Read Stability (RS) The ItemEnt bean was cached for 20 minute intervals using the WebSphere Lifetime in Cache Mechanism. Only the data inside the bean was cached.
Durability Requirement Info: To ensure database durability, RAID 1 (mirror disks) was used for the database files and logs on the two Sun StorEdge 3320 arrays.
Storage Requirement Info: An 75 minute run at an injection rate of 372 increased storage by 318 MB This extrapolates to 6.1 GB of storage for a 24 hour run. The database is configured with 1752 GB of storage. Each Sun StorEdge 3320 SCSI Array was configured as a single RAID 1 logical drive.
Argument Passing Semantics: WebSphere Application Server V6.1 uses pass-by-value as required by the EJB Specification.

Bill of Materials



Supplier	Description                               	Product No.       	Qty
--------	----------------------------------------  	------------------	---
Sun		Sun Fire T2000, 1x1.2 GHz T1, 32 GB		T20Z108B-32GA2D		1
Sun		Solaris 10 6/06 Media KIT			SOLZ9-10EC9A7M		1
Sun		SunSpectrum Upgrade: 3Y GOLD, 24x7		W9D-T2000-8-24-3G	1

Sun	 	X4200 Base Model - Chassis, Motherboard		A65-ZV			1
Sun		Opteron 275 - 2.2GHz/1MB			8037A-Z			2
Sun		4GB DDR1-400 Memory (2x2GB)			8023A-Z			4
Sun		73GB 10K SAS HDD				RA-SS2CD-73G10KZ	2
Sun		Redundant Power Supply				8026A-Z			1
Sun		2Gb Single Port x86 HBA				SGPCI1SCSILM320-Z	2
Sun		Sun Fire X4200 Server upgrade to 3Y GOLD	W9D-A65-3G		1
Sun		Sun StorEdge 3320, 12 x 73GB, 1 RAID		XTA3320R01A1T876	2
Sun		SunSpectrum Upgrade: 3Y GOLD, 24x7		W9D-SE3320-24-3G	2
Sun		Solaris 10 1/06 Media KIT			SOLZ9-10DC9A7M		1

Sun		17" Entry Color Monitor			     	X7201A			1
Sun		USB Keyboard & Mouse			     	320-1266		1

CISCO/Linksys	24-Port 10/100/1000 Gigabit Switch		SR2024			1

IBM		IBM WebSphere Application Server		D5ALTLL			3
		Network Deployment Edition  Processors
		License & SW Maintenance 12 Months
IBM		Processors SW Maintenance Annual Renewal	E1ALVLL			6
		WAS Network Deployment

IBM		DB2 UDB ENTERPRISE SERVER EDITION PROCESSOR	D54PYLL			2
		LIC+SW MAINT 12 MO
IBM		DB2 UDB ENTERPRISE SERVER EDITION PROCESSOR	E01MXLL             	4
		SW MAINT RNWL 1 ANNIV

Other Benchmark Information

  
  
  
  This submission used the xerces implementation (version - XML4J 4.4.5) provided with WebSphere Application Server V6.1 in the
  Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_06-erdist-20060404 20060511).

General Notes

The only errors in the driver log files were those that are normally generated by this benchmark.

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 questions about this result, please contact the submitter: Sun Microsystems Inc.
For other inquiries, please contact webmaster@spec.org

Benchmark run on Thu Jul 27 19:42:05 PDT 2006 by SPECjAppServer2004 v1.05
Result submitted on Wed Aug 2 03:03:00 EDT 2006
Report generated by SPECjAppServer2004 Reporter v1.03

First published at SPEC.org on 17-Aug-2006