SPEC Seal of Reviewal SPECjAppServer®2004 Result
Copyright © 2004 Standard Performance Evaluation Corporation
BEA WebLogic Server 9.1 with DB2 8.2 on Sun Fire X4600 using Solaris Containers
1,000.86 SPECjAppServer2004 JOPS@Standard
Submitter:
Sun Microsystems Inc.
SPEC license # 6 Test date:
Jul-2006
Software Products
BEA WebLogic Server 9.1, Advantage Edition
Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit
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
Driver SW Config Satellite #2
Hardware Systems
J2EE AppServer and Database HW
Load Driver HW
Load Driver HW Emulator

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: 12 cores, 6 chips   DB Server CPUs: 4 cores, 2 chips
J2EE Instances: 6   DB Instances: 1
Other SUT Components:
   

Benchmark Settings
Dealer Injection Rate: 600   Ramp Up Time: 900 seconds
# of Dealer Agents: 9   Ramp Down Time: 300 seconds
# of Manufacturing Agents: 9   Steady State Time: 3,600 seconds
DB Load Injection Rate: 600   Trigger Time: 610 seconds

Detailed Results
Dealer Transaction Mix Count Tx. Mix
Purchase 540,275 24.99%
Manage 541,122 25.03%
Browse 1,080,392 49.98%
Total # Dealer Transactions 2,161,789
Total # Manufacturing Transactions 1,441,295
Response Times Average Maximum 90th% Reqd
Purchase 0.47 16.37 1.30 2.00
Manage 0.31 16.17 0.80 2.00
Browse 0.56 11.94 1.90 2.00
Manufacturing 1.57 11.47 2.25 5.00
Reproducibility Run (SPECjAppServer2004 JOPS) 1,000.86

BEA WebLogic Server 9.1, Advantage Edition
Vendor: BEA Systems, Inc. Availability: Apr-2006
CTS Version: 1.4 Date Passed CTS: Jun-2005
OS Name: Solaris 10 (64-bit)
EJB Protocol: RMI/T3

Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit
Vendor: Sun Microsystems, Inc. Availability: Nov-2005
OS Name: Solaris 10 (64-bit)

IBM DB2 Universal JDBC Drivers
Vendor: IBM Corporation Availability: Apr-2006
OS Name: Solaris 10 (64-bit)

IBM DB2 Universal Database v8.2.4 (64-bit)
Vendor: IBM Corporation Availability: Apr-2006
OS Name: Solaris 10 (64-bit)

J2EE Application Servers
J2EE Product: BEA WebLogic Server 9.1, Advantage Edition
JVM Product: Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit
JDBC Product: IBM DB2 Universal JDBC Drivers
Hardware: J2EE AppServer and Database HW
# of Instances: 6
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: -server -Xms3g -Xmx3g -Xmn800m -Xss128k -XX:+AggressiveHeap
-XX:+UseParallelGC -XX:ParallelGCThreads=4 -XX:PermSize=128m
-XX:MaxTenuringThreshold=3 -XX:LargePageSizeInBytes=2m -XX:SurvivorRatio=20
-XX:+UseParallelOldGC -Dweblogic.SocketReaders=1
Java process started in FX class using /usr/bin/priocntl -e -c FX

Used patch for CR204945.

Emulator SW Config
J2EE Product: BEA WebLogic Server 9.1, Advantage Edition
JVM Product: Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit
Hardware: Load Driver HW Emulator
# of Instances: 1
Notes / Tuning Information
JVM Options: -server -Xms3g -Xmx3g -Xmn800m -Xss128k
-XX:+AggressiveHeap -XX:+UseParallelGC -XX:ParallelGCThreads=4
-XX:LargePageSizeInBytes=4m -XX:MaxTenuringThreshold=3 -XX:SurvivorRatio=20
-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps
-XX:-TraceClassUnloading
-Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0
-Dweblogic.SocketReaders=1
Java process started in FX class using /usr/bin/priocntl -e -c FX

Database SW Config
DB Product: IBM DB2 Universal Database v8.2.4 (64-bit)
Hardware: J2EE AppServer and Database HW
# of Instances: 1
Notes / Tuning Information
Tuning performed by db2tune.sh script in the archive/Schema directory.
DB2 processes bound across 4 processor cores in the DB Container using pbind utility.
DB2 processes run in FX class using the priocntl utility.

Driver SW Config Primary
JVM Product: Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit
Hardware: Load Driver HW
# of Instances: 1
Notes / Tuning Information
JVM Options: -server -XX:+AggressiveHeap -XX:+UseParallelGC
-XX:LargePageSizeInBytes=4m -XX:-TraceClassUnloading
-Xms2g -Xmx2g -Xmn600m -XX:+DisableExplicitGC -Xbatch -Xss128k
-Dorg.omg.CORBA.ORBInitialHost=$JAS_MULTI_HOST Djava.naming.factory.initial=$JNDI_CLASS
-Djava.naming.provider.url=$NAMING_PROVIDER
-Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0

Driver SW Config Satellite #1
JVM Product: Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit
Hardware: Load Driver HW
# of Instances: 1
Notes / Tuning Information
JVM Options: -server -XX:+AggressiveHeap -XX:+UseParallelGC
-XX:LargePageSizeInBytes=4m -XX:-TraceClassUnloading
-Xms2g -Xmx2g -Xmn600m -XX:+DisableExplicitGC -Xbatch -Xss128k
-Dorg.omg.CORBA.ORBInitialHost=$JAS_MULTI_HOST -Djava.naming.factory.initial=$JNDI_CLASS
-Djava.naming.provider.url=$NAMING_PROVIDER
-Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0

Driver SW Config Satellite #2
JVM Product: Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit
Hardware: Load Driver HW Emulator
# of Instances: 1
Notes / Tuning Information
JVM Options: -server -XX:+AggressiveHeap -XX:+UseParallelGC
-XX:LargePageSizeInBytes=4m -XX:-TraceClassUnloading
-Xms2g -Xmx2g -Xmn600m -XX:+DisableExplicitGC -Xbatch -Xss128k
-Dorg.omg.CORBA.ORBInitialHost=$JAS_MULTI_HOST -Djava.naming.factory.initial=$JNDI_CLASS
-Djava.naming.provider.url=$NAMING_PROVIDER
-Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0

J2EE AppServer and Database HW (SUT hardware)
Hardware Vendor: Sun Microsystems, Inc. OS Vendor: Sun Microsystems, Inc.
Model Name: Sun Fire X4600 OS Name: Solaris 10 6/06 (64-bit)
Processor: AMD Opteron 885 Filesystem: UFS
MHz: 2600 Disks: 4x73Gb 10K RPM SAS
# of CPUs: 16 cores, 8 chips, 2 cores/chip Network Interface: (4) 1000BaseT onboard Ethernet
Memory (MB): 65536 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: 2MB per chip H/W Available: Jul-2006
Other Cache: OS Available: Jun-2006
Notes / Tuning Information
Six application server instances and one single database server instance
hosted in separate Solaris Containers. Six application server instances
were each bound to a 2-core processor set and the single database instance
bound to a 4-core processor set using the Resource Pools facility. Configuration
informaton for the Containers and Resource Pools are included in the FDA.
Configuration information to setup IPC resources for DB2 database
in Solaris Containers included in the FDA.
System Tuning:
eeprom e1000g_intpt_bind_cpus=12,0,4,8
eeprom mpt_intpt_bind_cpus=14,15
UFS options for database files: noatime,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 131072
ndd -set /dev/tcp tcp_recv_hiwat 131072
ndd -set /dev/tcp tcp_naglim_def 1

Load Driver HW (non-SUT hardware)
Hardware Vendor: Sun Microsystems, Inc. OS Vendor: Sun Microsystems, Inc.
Model Name: Sun Fire V440 OS Name: Solaris 10 6/06 (64-bit)
Processor: UltraSPARC IIIi Cu Filesystem: UFS
MHz: 1600 Disks: 2 x 73GB Internal Disk
# of CPUs: 4 cores, 4 chips, 1 core/chip Network Interface: (2) Onboard 1000BaseT Ethernet
Memory (MB): 16384 Other Hardware:
L1 Cache: 32KB(I)+64KB(D) on chip # of Systems: 2
L2 Cache: 1MB(I+D) on chip H/W Available: Nov-2004
Other Cache: OS Available: Jun-2006
Notes / Tuning Information
System Tuning in /etc/system:
set ce:ce_bcopy_thresh=256
set ce:ce_dvma_thresh=256
set ce:ce_taskq_disable=1
set ce:ce_ring_size=256
set ce:ce_comp_ring_size=1024
set ce:ce_tx_ring_size=4096

Load Driver HW Emulator (non-SUT hardware)
Hardware Vendor: Sun Microsystems, Inc. OS Vendor: Sun Microsystems, Inc.
Model Name: Sun Fire V890 OS Name: Solaris 10 6/06 (64-bit)
Processor: UltraSPARC IV+ Filesystem: UFS
MHz: 1500 Disks: 6 x 73Gb FC
# of CPUs: 16 cores, 8 chips, 2 cores/chip Network Interface: (1) Onboard 1000BaseT Ethernet + (1) Sun GigaSwift Network Card
Memory (MB): 65536 Other Hardware:
L1 Cache: 64KB(I)+64KB(D) # of Systems: 1
L2 Cache: 2MB(I+D) per chip H/W Available: Oct-2005
Other Cache: 32MB(I+D) per chip OS Available: Jun-2006
Notes / Tuning Information
System Tuning in /etc/system:
set ce:ce_bcopy_thresh=256
set ce:ce_dvma_thresh=256
set ce:ce_taskq_disable=1
set ce:ce_ring_size=256
set ce:ce_comp_ring_size=1024
set ce:ce_tx_ring_size=4096

Benchmark Modifications
Schema Modifications:
  Tablespace sizes were increased to support the Injection rate.
  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 15 minute intervals by setting
  concurrency-strategy to ReadOnly and
  read-timeout-seconds to 900
  in bea-orders.xml deployment descriptor.
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.
  
  The Sun Fire X4600 server has a pair of mirrored disks
  (using onboard controller) to provide durability for all the
  application server logs and filestore for JMS persistence.
Storage Requirement Info:
  An 80 minute run at an injection rate of 600 increased storage by 544 MB
  This extrapolates to 9.56 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:
  BEA WebLogic 9.1 uses pass-by-value as required by the EJB Specification.

Bill of Materials


Supplier  Description                                Product No.          Qty
--------  ----------------------------------------   ------------------   ---
Sun       Sun Fire X4600, 8x2.6 GHz AMD 885, 32 GB   A67-QGZ8-4S-032CB1    1
Sun	  73 GB SAS Disk			     RA-SS2CD-73G10KZ	   2
Sun	  4 GB Memory Kit			     8121A-Z               8
Sun       Solaris 10 6/06 Media KIT                  SOLZ9-10EC9A7M        1
Sun	  Sun StorEdge PCI U320 SCSI Host Adapter    SGXPCI1SCSILM320-Z	   2
Sun       SunSpectrum Upgrade: 3Y GOLD, 24x7         W9D-A67-8-24-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	  17" Entry Color Monitor		     X7201A		   1
Sun	  USB Keyboard & Mouse			     320-1266	           1

BEA       BEA WebLogic Server 9.1 License,  Advantage Edition              6
BEA       3-year 24x7x4 Support for WebLogic Server                        6

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
  The submission used round-robin DNS for load-balance of
  all network requests. The DNS server was hosted
  on the Sun Fire X4600.
  
  This submission used the xerces implementation 2.6.2 provided with WebLogic 9.1

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

Copyright © 2004 Standard Performance Evaluation Corporation

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