SPEC Seal of Reviewal SPECjEnterprise®2010 Result
Copyright © 2009-2010 Standard Performance Evaluation Corporation
WebSphere Application Server V7 on IBM System x3650 and DB2 9.7 on IBM System x3850
1,013.40 SPECjEnterprise2010 EjOPS
Submitter:
IBM Corporation
SPEC license # 11 Test date:
Dec-2009
Software Products
WebSphere Application Server V7 (Level 7.0.0.5)
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 FP1
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: 1   DB Server Nodes: 1
JEE Server CPUs: 8 cores, 2 chips   DB Server CPUs: 12 cores, 2 chips
JEE Instances: 2   DB Instances: 1
Other SUT Components:
   NETGEAR GS116 16-port 10/100/1000Mbps Gigabit Switch

Benchmark Settings
Dealer Injection Rate: 635   Ramp Up Time: 1,200 seconds
DB Load Injection Rate: 700   Steady State Time: 3,600 seconds
# of Dealer Agents: 6,350   Ramp Down Time: 300 seconds
# of Manufacturing Agents: 1,905  

Detailed Results
Dealer Transaction Mix Count Tx. Mix Failure Count
Purchase 574,548 24.98% 0
Manage 575,212 25.01% 0
Browse 1,150,271 50.01% 0
Total # Dealer Transactions 2,300,031
Manufacturing Transaction Mix Count Tx. Mix Failure Count
CreateVehicleEJB 673,986 49.99% 155
CreateVehicleWS 674,208 50.01% 148
Total # Manufacturing Transactions 1,348,194
Response Times Average Standard Deviation Maximum 90th% Reqd
Purchase 0.232 0.32 4.796 0.590 2.000
Manage 0.163 0.19 7.198 0.370 2.000
Browse 0.321 0.33 3.441 0.720 2.000
CreateVehicleEJB 0.112 0.11 1.461 0.290 5.000
CreateVehicleWS 0.088 0.06 1.116 0.150 5.000
Reproducibility Run (SPECjEnterprise2010 EjOPS) 1,014.20

WebSphere Application Server V7 (Level 7.0.0.5)
Vendor: IBM Corporation Availability: Jun-2009
CTS Version: 5.0 Date Passed CTS: Sep-2008
OS Name: Novell SUSE Linux Enterprise Server 10 SP2
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-2009
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 FP1
Vendor: IBM Corporation Availability: Nov-2009
OS Name: Novell SUSE Linux Enterprise Server 10 SP2

JEE Application Server
JEE Product: WebSphere Application Server V7 (Level 7.0.0.5)
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: 2
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:
-Xms6144m -Xmx6144m -Xss128k -Xgcpolicy:gencon -Xnoloa -Xmo1000m -Xmn5144m -Xtrace:none -Xlp
-Xgcthreads8 -Xdisableexplicitgc -Dcom.ibm.CORBA.FragmentSize=3000 -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 (Level 7.0.0.5)
JVM Product: IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64)
Hardware: Emulator HW
# of Instances: 1
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 FP1
Hardware: Database Server HW
# of Instances: 1
Character Set: UTF-8
Notes / Tuning Information
DB2_USE_ALTERNATE_PAGE_CLEANING=ON
DB2_KEEPTABLELOCK=ON
DB2_APM_PERFORMANCE=ON
DB2SPINLATCHES=0:0
DFT_MON_BUFPOOL on
DFT_MON_LOCK on
DFT_MON_SORT off
DFT_MON_STMT off
DFT_MON_TIMESTAMP on
DFT_MON_UOW on
DFT_MON_TABLE off
CPUSPEED -1
SVCENAME 60004
LOGBUFSZ 4096
LOGPRIMARY 52
SOFTMAX 200
CHNGPGS_THRESH 99
LOGFILSIZ 65535
LOGRETAIN on

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: 1
Notes / Tuning Information
-server -Xms4096M -Xmx4096M -Djava.net.preferIPv4Stack=true
-Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0 -Dcom.ibm.websphere.naming.jndicache.cacheobject=none
-Dcom.ibm.websphere.naming.hostname.normalizer=...none... -DdisableWSAddressCaching=true
-Dcom.ibm.CORBA.ConnectionMultiplicity=20

JEE AppServer HW (SUT hardware)
Hardware Vendor: IBM Corporation OS Vendor: Novell
Model Name: IBM System x3650 M2 OS Name: Novell SUSE Linux Enterprise Server 10 SP2
Processor: Intel Xeon X5570 (Intel Turbo Boost Technology up to 3.33GHz) Filesystem: Reiser
MHz: 2933 Disks: 1x146GB 10K SAS
# of CPUs: 8 cores, 2 chips, 4 cores/chip (8 HW threads/chip) Network Interface: (4) 1000BaseT Ethernet
Memory (MB): 16384 Other Hardware:
DIMM[0] Count: 8 DIMM[0] Size: 2048
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: Jun-2009
Other Cache: 8 MB I+D on chip per chip OS Available: May-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.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

Database Server HW (SUT hardware)
Hardware Vendor: IBM Corporation OS Vendor: Novell
Model Name: IBM System x3850 M2 OS Name: Novell SUSE Linux Enterprise Server 10 SP2
Processor: Intel Xeon X7460 Filesystem: Reiser
MHz: 2666 Disks: 2x146Gb 10K 2.5" Hot-Swap SAS HDD
# of CPUs: 12 cores, 2 chips, 6 cores/chip Network Interface: (2) 1000BaseT Ethernet
Memory (MB): 65536 Other Hardware: 1xDS4800 Disk System, 2xDS4000 EXP810 Expansion Disk Arrays, 32x36.4GB 15K E-DDM Disks
DIMM[0] Count: 32 DIMM[0] Size: 2048
L1 Cache: 32KB(I) + 32KB(D) on chip, per core # of Systems: 1
L2 Cache: 9MB(I+D) on chip, per chip (3MB shared / 2 cores) H/W Available: Jun-2009
Other Cache: 16MB(I+D) on chip, per chip OS Available: Sept-2008
Notes / Tuning Information
fs.file-max = 1048576
kernel.sem = 4096 512000 1600 9000
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

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: 1
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

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: (2) 1000BaseT
Memory (MB): 16384 Other Hardware:
L1 Cache: 32KB(I)+32KB(D) # of Systems: 1
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:
  No modifications to the schema where made.
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 OpenJPA Data 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 33GB disks were used for the log.
Storage Requirement Info:
  Over the course of a 85 minute run at an injection rate of
    635, the database storage for database system increased by
    6.24 GB.  Given a linear scale, a 24 hour run at the same
    injection rate would increase storage for database system
    by 105.71 GB.  One RAID10 disk arrays were used to create the
    filesystem space for the database.  The array contained
    16 x 33GB disks providing 267 Gb GB of storage.

Bill of Materials
Supplier  Description                                   Product #          Qty
--------  -------------------------------------------   ----------------   ---
IBM       IBM System x3850 M2                           7233AC1              1
-          2xSix Core Intel Xeon Processor X7460
-            (2.67GHz 16MB L3 130w)
-          64GB RAM (32x2GB DIMMS), 2x146GB 10k SAS HDD
IBM       DS4800 Disk System Model 82 (4 GB Cache)      1815-82A             1
IBM       DS4000 EXP810 Expansion Unit Model 81         1812-81A             2
IBM       4 Gbps FC, 36.4 GB/15K E-DDM                  5433                32
IBM       3 Year Onsite Repair 24x7 4 Hour Response     6756001              1
IBM       SUSE Linux Enterprise Server w/ 3yr support   5639S1X              1
...
IBM       IBM System x3650 M2   325254-B21              7947AC1              1
-          2xIntel Xeon Processor X5570 4C
-            (2.93GHz 8MB L3 Cache 1333MHz 95w)
-          16GB RAM (8x2GB DIMMS), 1x146GB 10k SAS HDD
IBM       3 Year Onsite Repair 24x7 4 Hour Response     6756025
IBM       SUSE Linux Enterprise Server w/ 3yr support   5639S1X              1
...
CDW       NETGEAR GS116 16-port 10/100/1000Mbps         638864               1
-          Gigabit Switch
CDW       NETGEAR 3 Year ProSupport Maintenance         PMB0331NA            1
-          Contract - OnCall 24x7 - Category 1
IBM       DB2 Enterprise Server Edition 9.7             D597RLL            12*
-           Lic+SW Maint 12 Months
IBM       DB2 Enterprise Server Edition 9.7             E00BILL             24
-           SW Maint Rewl 1 Anniv
IBM       WebSphere Application Server V7               D55W8LL            8**
-           Lic+SW Maint 12 Months
IBM       WebSphere Application Server V7               E1CBBLL             16
-           SW Maint Rewl 1 Anniv
...
* Note:  Pricing for DB2 is based on Value Units (VU).  Each Intel core is 50 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

Copyright © 2009-2010 Standard Performance Evaluation Corporation

First published at SPEC.org on 02-Jan-2010