SPEC Seal of Reviewal SPECjAppServer®2004 Result
Copyright © 2004 Standard Performance Evaluation Corporation
Sun Java Application Server 9.1 on Sun Fire T2000
883.66 SPECjAppServer2004 JOPS@Standard
Submitter:
Sun Microsystems Inc.		 SPEC license # 6 Test date:
Jun-2007
Software Products
Sun Java System Application Server 9.1
Jakarta Tomcat 5.5.23
Java (TM) 2 Platform Standard Edition Development Kit 6.0 Update 2 32-bit
DataDirect Connect for JDBC 3.6
IBM DB2 9.1 		Software Configurations
J2EE Application Servers
Emulator SW Config
Database SW Config
Driver SW Config 		Hardware Systems
J2EE AppServer HW
Database Server HW
Load Driver HW Primary (Emulator)
Load Driver HW Secondary

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, 8 cores/chip (4 threads/core)   DB Server CPUs: 6 cores, 1 chip, 6 cores/chip (4 threads/core)
J2EE Instances: 1   DB Instances: 1
Other SUT Components:
   

Benchmark Settings
Dealer Injection Rate: 531   Ramp Up Time: 600 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: 361 seconds

Detailed Results
Dealer Transaction Mix Count Tx. Mix
Purchase 479,343 25.03%
Manage 477,948 24.96%
Browse 957,765 50.01%
Total # Dealer Transactions 1,915,056
Total # Manufacturing Transactions 1,266,131
Response Times Average Maximum 90th% Reqd
Purchase 0.41 15.61 0.80 2.00
Manage 0.31 12.92 0.70 2.00
Browse 0.52 12.20 1.00 2.00
Manufacturing 2.43 11.62 4.75 5.00
Reproducibility Run (SPECjAppServer2004 JOPS) 884.40

Sun Java System Application Server 9.1
Vendor: Sun Microsystems, Inc. Availability: Sep-2007
CTS Version: CTS EE 5 Date Passed CTS: Sep-2007
OS Name: Solaris 10 08/07 (64-bit)
EJB Protocol: RMI/IIOP

Jakarta Tomcat 5.5.23
Vendor: Apache Software Foundation Availability: Sep-2006

Java (TM) 2 Platform Standard Edition Development Kit 6.0 Update 2 32-bit
Vendor: Sun Microsystems, Inc. Availability: Jul-2007
OS Name: Solaris 10 08/07 (64-bit)

DataDirect Connect for JDBC 3.6
Vendor: Sun OEM Version Availability: Sep-2007
OS Name: Solaris 10 08/07 (64-bit)

IBM DB2 9.1
Vendor: IBM Corporation Availability: Feb-2007
OS Name: Solaris 10 6/06 (64-bit)

J2EE Application Servers
J2EE Product: Sun Java System Application Server 9.1
JVM Product: Java (TM) 2 Platform Standard Edition Development Kit 6.0 Update 2 32-bit
JDBC Product: DataDirect Connect for JDBC 3.6
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 
Tunings in domain.xml:
JVM Options:  -server -XX:+AggressiveHeap
    -Xmx2560m -Xms2560m -Xmn1560m -Xss128k
    -XX:+DisableExplicitGC
    -XX:ParallelGCThreads=24
    -XX:LargePageSizeInBytes=256m
    -XX:+UseParallelOldGC
    -Dcom.sun.enterprise.server.ss.ASQuickStartup=false
    -DAllowManagedFieldsInDefaultFetchGroup=true
    -DAllowMediatedWriteInDefaultFetchGroup=true
    -Dcom.sun.ejb.containers.readonly.relative.refresh.mode=true
    -Dimq.jmsra.direct=true
    -XX:+AggressiveOpts -XX:-UseBiasedLocking
JDBC Pool: max-pool-size=200, steady-pool-size=200
JDBC: forceFixRow=true, stripNewlines=false
JDBC: MaxPooledStatements=200
HTTP Listener: acceptor-threads=4
HTTP ThreadPool: max-thread-pool-size=55, min-thread-pool-size=1
ORB ThreadPool: max-thread-pool-size=45, min-thread-pool-size=45
Default ThreadPool: max-thread-pool-size=40, min-thread-pool-size=40
JMS Connection Pool: max size 250
Transaction Service: logging to jdbc/SPECDB
General Tunings:
All application servers run in FX class via priocntl command

Emulator SW Config
JVM Product: Java (TM) 2 Platform Standard Edition Development Kit 6.0 Update 2 32-bit
Web Product: Jakarta Tomcat 5.5.23
Hardware: Load Driver HW Primary (Emulator)
# of Instances: 1
Notes / Tuning Information 
JVM Options: -server
     -Xmx1024m

HTTP Thread Pool Size: min=25, max=500

Database SW Config
DB Product: IBM DB2 9.1
Hardware: Database Server HW
# of Instances: 1
Notes / Tuning Information 
Tuning performance by db2tune.sh script in FDA
DB2 processes run in FX class using priocntl
DB2 processes bound across all processor cores using pbind

Driver SW Config
JVM Product: Java (TM) 2 Platform Standard Edition Development Kit 6.0 Update 2 32-bit
Hardware: Load Driver HW Primary (Emulator)
# of Instances: 1
Notes / Tuning Information 
JVM Options:  -server -XX:+DisableExplicitGC
-Xms1500m -Xmx1500m -Xss128k -Djava.naming.factory.initial=com.sun.appserv.naming.S1ASCtxFactory
-Djava.naming.provider.url=iiop://ecapps:3700
-Djava.naming.provider.url.pkgs=com.sun.enterprise.naming
-Dcom.sun.appserv.iiop.endpoints=ecapps:3700

J2EE AppServer HW (SUT hardware)
Hardware Vendor: Sun Microsystems, Inc. OS Vendor: Sun Microsystems, Inc.
Model Name: Sun Fire T2000 Server OS Name: Solaris 10 08/07 (64-bit)
Processor: Sun UltraSPARC T1 Filesystem: UFS
MHz: 1400 Disks: 4x73Gb 10K RPM SAS
# of CPUs: 8 cores, 1 chip, 8 cores/chip (4 threads/core) Network Interface: (4) on-board 1000BaseT Ethernet
Memory (MB): 65536 Other Hardware:
L1 Cache: 16KB(I)+8KB(D) per core # of Systems: 1
L2 Cache: 3MB per chip H/W Available: Jan-2007
Other Cache: OS Available: Aug-2007
Notes / Tuning Information 
dladm used to aggregate two network ports for clients
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

Database Server HW (SUT hardware)
Hardware Vendor: Sun Microsystems, Inc. OS Vendor: Sun Microsystems, Inc.
Model Name: Sun Fire T2000 Server OS Name: Solaris 10 6/06 (64-bit)
Processor: UltraSPARC T1 Filesystem: UFS
MHz: 1000 Disks: 2x73Gb 10K RPM Ultra320 SCSI
# of CPUs: 6 cores, 1 chip, 6 cores/chip (4 threads/core) Network Interface: (4) Onboard 1000BaseT Ethernet
Memory (MB): 8192 Other Hardware: 2 Sun StorEdge SE3320 Array (12 x 73GB UltraSCSI Disk Array)
L1 Cache: 16KB(I)+8KB(D) per core # of Systems: 1
L2 Cache: 3MB per chip H/W Available: Dec-2005
Other Cache: OS Available: Jun-2006
Notes / Tuning Information 
UFS options for /specdb: noatime,forcedirectio

Load Driver HW Primary (Emulator) (non-SUT hardware)
Hardware Vendor: Sun Microsystems, Inc. OS Vendor: Sun Microsystems, Inc.
Model Name: Sun File V440 Server OS Name: Solaris 10 6/06 (64-bit)
Processor: UltraSPARC IIIi Filesystem: UFS
MHz: 1280 Disks: 4 x 36GB
# 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) # of Systems: 1
L2 Cache: 1MB H/W Available: Oct-2003
Other Cache: OS Available: Jun-2006
Notes / Tuning Information 
Tunings 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
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 Secondary (non-SUT hardware)
Hardware Vendor: Sun Microsystems, Inc. OS Vendor: Sun Microsystems, Inc.
Model Name: Sun Fire V440 Server OS Name: Solaris 10 6/06 (64-bit)
Processor: UltraSPARC IIIi Filesystem: UFS
MHz: 1280 Disks: 4 x 36GB
# 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) # of Systems: 2
L2 Cache: 1MB H/W Available: Oct-2003
Other Cache: OS Available: Jun-2006
Notes / Tuning Information 
Tunings 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
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

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: 
  BEAN				SPEC_REQUIREMENT	Deployment
  Corp.CustomerEnt		Repeatable Read		RS
  Corp.CustomerInventoryEnt	Repeatable Read		RS
  Mfg.InventoryEnt		Repeatable Read		RS
  Mfg.WorkOrderEnt		Repeatable Read		RS
  Orders.OrderEnt		Repeatable Read		RS
  Orders.OrderLineEnt		Repeatable Read		RS
  Supplier.POEnt		Repeatable Read		RS
  Supplier.POLineEnt		Repeatable Read		RS
  Supplier.SComponentEnt	Repeatable Read		RS
  Util.SequenceEnt		Repeatable Read		RS
  Mfg.AssemblyEnt		Read Committed		CS
  Mfg.BomEnt			Read Committed		CS
  Mfg.ComponentEnt		Read Committed		CS
  Mfg.LargeOrderEnt		Read Committed		CS
  Mfg.PartEnt			Read Committed		CS
  Orders.ItemEnt		Read Committed		CS
  Supplier.SupplierCompEnt	Read Committed		CS
  Supplier.SupplierEnt		Read Committed		CS
  
  The ItemEnt bean was cached for 20 minute intervals by setting
  is-read-only-bean=true and refresh-period-in-seconds=1200 in the
  sun-orders.xml deployment descriptor.
  Only the data inside the bean was cached.
  
  Repeatable read beans were accessed using DB2 isolation level RS
  Read committed beans were accessed using DB2 isolation level CS
Durability Requirement Info: 
  To ensure database durability, RAID 1 (mirror disks)
  was used for the database maintained on the
  Sun StorEdge 3320 Arrays.
  
  The application server has a pair of mirrored disks
  (using Solaris Volume Manager) to provide
  durability for the message queues.
Storage Requirement Info: 
  A 75 minute run at an injection rate of 531 increased storage by 451 MB
  This extrapolates to 10.5 GB of storage for a 24 hour run.
  The database is configured with 1752 GB of mirrored data storage.
Argument Passing Semantics: 
  Sun Java System Application Server 9.1 uses pass-by-value semantics by default.

Bill of Materials 


Supplier  Description                                Product #            Qty
--------  ----------------------------------------   ------------------   ---
Sun	  Sun Fire T2000, 1x1.4 GHz, 64 GB mem	     T20Z108C-64GA2G       1
Sun 	  73 GB 10K 2.5" SAS Disk		     XRA-SS2CD-73G10K      2
Sun	  Solaris 10 08/07 Media KIT		     SOLZ9-10GC9A7M	   1
Sun 	  SunSpectrum Upgrade: 3YGOLD, 24x7	     W9D-T2000-8-24-3G	   1

Sun	  Sun Fire T2000, 1x1.0 GHz, 8 GB mem	     T20Z106A-08GA2D       1
Sun	  Solaris 10 6/06 Media KIT		     SOLZ9-10FC9A7M	   1
Sun	  Ultra320 SCSI Dual Channel Adapter	     SGXPCI2SCSILM320-Z    1
Sun 	  SunSpectrum Upgrade: 3YGOLD, 24x7	     W9D-T2000-6-24-3G	   1

Sun	  Sun StorEdge 3320, 12 x 73 GB, 1 RAID	     XTA3320R01A1T876      2
Sun	  SunSpectum Upgrade: 3Y GOLD, 24x7	     W9D-SE3320-24-3G	   2
Sun       17" Entry Color Monitor                    X7204A                1
Sun       XVR-200 Graphics Accelerator               X3777                 2
Sun       USB Keyboard                               320-1271              1
Sun       USB Mouse                                  320-2632              1


Sun	  Sun Java System Application Server 9.1     ASE29-00P-B929	   1
Sun	  Sun Java System Application Server 9.1     SJSAS-PE9F-1PR	   3
	    Premium Support per CPU for 1 years

IBM	  DB2 WSE CPU Option Processor(s)	     D51NDLL		   1.8
	  License & SW Maintenance 12 Months
IBM	  DB2 WSE CPU Option Processor(s) 	     E00IHLL   		   3.6
	  SW Maintenance Annual Renewal

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

Recoverable 2-phase transactions were used to coordinate the
the database server and JMS server using Sun's Last Agent
Optimization; the 1PC database transactions and transaction
written to the database in a single transaction.

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

When DB2 UDB server modifies a database table, 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" checkpoints to write least-recently-used database
pages to disk independent of transaction commit. However, enough log
information to redo/udo the change to a database page is committed to disk
before the database page itself is written. This protocol therefore renders
checkpoints 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 10-Jul-2007