SPEC Seal of Reviewal SPECjAppServer2002 Result
Copyright © 2002 Standard Performance Evaluation Corporation
WebSphere 5.0.1 Application Server on eServer xSeries 360 Cluster
448.12 TOPS@MultipleNode
647.52 US$/TOPS@MultipleNode
Submitter:
IBM Corporation		 SPEC license # 11 Test date:
Jun-2003		 EJB Container Avail: May-2003
EJB Container JVM Avail: May-2003
Software
EJB Container
Supplier Domain Container
Emulator Container
Database
JDBC
Other Software 		Hardware
J2EE Application Server
Database Server
Load Driver 		Benchmark
Modifications
Configuration
Other Info
General Notes 		Links
System Configuration Diagram

Full Disclosure Archive


Benchmark Settings
Orders Injection Rate: 260 Ramp Up Time: 600 seconds
# of Order Agents: 1 Ramp Down Time: 300 seconds
# of Manufacturing Agents: 1 Steady State Time: 1800 seconds
DB Load Injection Rate: 260 Trigger Time: 276 seconds
Total System Cost: US$290,164

Detailed Results
Order Transaction Mix Count Tx. Mix
New Order 232,158 49.87%
Change Order 93,478 20.08%
Order Status 93,287 20.04%
Customer Status 46,622 10.01%
Total # Order Transactions 465,545
Total # Manufacturing Transactions 341,066
Response Times Average Maximum 90th% Reqd
New Order 0.77 5.17 1.90 2.00
Change Order 0.41 2.25 0.80 2.00
Order Status 0.20 1.83 0.50 2.00
Customer Status 0.26 1.83 0.60 2.00
Manufacturing 2.23 5.09 3.00 5.00
Reproducibility Run (TOPS) 448.81

EJB Container
Name: WebSphere 5.0.1 Application Server, Network Deployment JVM Name: J2RE 1.3.1 IBM Windows 32 build cn131-20030329
Vendor: IBM Corporation JVM Vendor: IBM Corporation
Available: May-2003 Available: May-2003
Instances: 2
Passed CTS: May-2003
Protocol: RMI/IIOP
Tuning Information 
EJB Container Cache Size: 8191
ORB Service Minimum Thread Pool Size: 37
ORB Service Maximum Thread Pool Size: 37
com.ibm.CORBA.FragmentSize=0
JVM Tuning Information 
Initial Heap Size: 1024
Maximum Heap Size: 1024

Supplier Domain Container
Name: WebSphere 5.0.1 Application Server, Network Deployment JVM Name: J2RE 1.3.1 IBM Windows 32 build cn131-20030329
Vendor: IBM Corporation JVM Vendor: IBM Corporation
Available: May-2003 Available: May-2003
Tuning Information 
Web Container Minimum Thread Pool Size: 10
Web Container Maximum Thread Pool Size: 30

Note: Secondary nodes used Web Container Minimum and Maximum Thread
Pool Sizes of 1 and 5 respectively.
JVM Tuning Information 
Initial Heap Size: 1024
Maximum Heap Size: 1024

Emulator Container
Name: WebSphere 5.0.1 Application Server, Network Deployment JVM Name: J2RE 1.3.1 IBM Windows 32 build cn131-20030329
Vendor: IBM Corporation JVM Vendor: IBM Corporation
Available: May-2003 Available: May-2003
Tuning Information 
Web Container Minimum Thread Pool Size: 50
Web Container Maximum Thread Pool Size: 50
Web Container Growable Thread Pool: true
JVM Tuning Information 
Initial Heap Size: 256
Maximum Heap Size: 512

Database
Name: DB2 Universal Database v8.1 FP3, Workgroup Server Unlimited Edition
Vendor: IBM Corporation
Available: Aug-2003
Tuning Information 
The db2tune.bat script included within the FDA was used to modify the configuration
for the specdb database and associated database manager. This configuration information
is also provided by the following files in the FDA.

db2set.txt
dbm_config.txt
specdb_config.txt

JDBC
Name: DB2 v8.1 Type 2 JDBC Driver (08.01.0002)
Vendor: IBM Corporation
Available: Aug-2003
Tuning Information 
DB2 v.8 Type 2 JDBC Driver
Implementation class:   COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource

SPECDB Datasource
JNDI Name:              jdbc/SPECDB
Minimum pool size:      48
Maximum pool size:      48
Statement cache size:   51

SPECUtilDB Datasource
JNDI Name:              jdbc/SPECUtilDB
Minimum pool size:      10
Maximum pool size:      10
Statement cache size:   5

Other Software
Name:
Vendor:
Available:
Tuning Information 

   		
  

 













J2EE Application Server (2 systems)




 

  

Hardware Vendor:
IBM Corporation
OS Vendor:
Microsoft Corporation
  

  

Model Name:
IBM eServer xSeries x360
OS Name:
Windows 2000 Server
  

  

Processor:
Intel Xeon MP
Filesystem:
NTFS
  

  

MHz:
2800
Disks:
36.4GB Ultra 160 SCSI
  

  

# of CPUs:
4 cores, 4 chips, 1 core/chip
Network Interface:
1000BASE-TX (Gigabit) Ethernet
  

  

Memory (MB):
3072
Other Hardware:

  

  

L1 Cache:
12Kuops(I)+8KB(D)
# of Systems:
2
  

  

L2 Cache:
512KB
H/W Available:
Jun-2003
  

  

Other Cache:
2048KB
OS Available:
Jun-2003
  

 





 

  

Notes / Tuning Information
  

  

   

The following parameters were added to the Windows registry:

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters"TcpTimedWaitDelay"=dword:0000001e]
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters"MaxUserPort"=dword:0000fffe]


   		
  

 













Database Server (1 system)




 

  

Hardware Vendor:
IBM Corporation
OS Vendor:
Microsoft Corporation
  

  

Model Name:
IBM eServer xSeries x360
OS Name:
Windows 2000 Advanced Server
  

  

Processor:
Intel Xeon MP
Filesystem:
NTFS
  

  

MHz:
2800
Disks:
18.2GB Ultra 160 SCSI
  

  

# of CPUs:
2 cores, 2 chips, 1 core/chip
Network Interface:
(2)1000BASE-TX (Gigabit) Ethernet
  

  

Memory (MB):
3072
Other Hardware:
(2) EXP300 Storage Expansion Units with a total of 21 18GB Ultra 160 SCSI disks
  

  

L1 Cache:
12Kuops(I)+8KB(D)
# of Systems:
1
  

  

L2 Cache:
512KB
H/W Available:
Jun-2003
  

  

Other Cache:
2048KB (L3 cache)
OS Available:
Jun-2003
  

 





 

  

Notes / Tuning Information
  

  

   

The following parameters were added to the Windows system registry:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\"TcpTimedWaitDelay"=dword:0000001e]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\"MaxUserPort"=dword:0000fffe]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\"LargeSystemCache"=dword:00000000]



   		
  

 













Load Driver (1 system)




 

  

Hardware Vendor:
IBM Corporation
OS Vendor:
Microsoft Corporation
  

  

Model Name:
IBM eServer xSeries x350
OS Name:
Windows 2000 Server
  

  

Processor:
Pentium III Xeon
Filesystem:
NTFS
  

  

MHz:
900
Disks:
18GB Ultra 160 SCSI
  

  

# of CPUs:
4 cores, 4 chips, 1 core/chip
Network Interface:
1000BASE-TX (Gigabit) Ethernet
  

  

Memory (MB):
4096
Other Hardware:

  

  

L1 Cache:
16KBI+16KBD (on chip)
# of Systems:
1
  

  

L2 Cache:
2MB (on chip)
H/W Available:
Jun-2000
  

  

Other Cache:

OS Available:
Jun-2003
  

 





 

  

Notes / Tuning Information
  

  

   

The load driver utilized the IBM JDK included with WebSphere 5.0.1
Application Server (J2RE 1.3.1 IBM Windows 32 build cn131-20030329).


   		
  

 













Benchmark Modifications




Schema Modifications:

  The scripts used to create the database are located within the FDA. Two additional
  indicies were added for the M_LargeOrder table in the manufacturing domain.
  The DDL to create these indicies are included in the FDA /schema/sql directory.






Load Program Modifications:

  No changes were made to the load program.






Reference Bean Modifications:

  No modifications were made to the reference beans.














Benchmark Configuration Information




Persistence Mode Used:

  All beans were deployed using Container Managed Persistence (CMP).






Isolation Requirement Info:

  All beans were deployed with the isolation level set to REPEATABLE_READ. DB2
  translates this isolation level to Read Stability.  Read Stability ensures
  that all rows referenced in a transaction have a read-lock associated with
  them to ensure that other transactions cannot change the rows until the first
  referencing transaction completes.






Durability Requirement Info:

  To ensure database durability, RAID-1E enhanced disk mirroring was used for
  the database log files.






Storage Requirement Info:

  Over the course of a 45 minute run at an injection rate of 260, database storage
  increased  150.5 MB. Given a linear scale, an eight hour run at the same injection
  rate would increase storage 1606 MB. The disk array enclosure was configured
  with 118 GB of disk storage.






Argument Passing Semantics:

  WebSphere 5.0.1 Application Server uses pass-by-value semantics by default.














Other Benchmark Information





  This submission used the xerces.jar (version - XML4J 4.0.10) provided with WebSphere Application Server 5.0.1.














General Notes





No errors were encoutered in the driver error logs.










For questions about this result, please contact the submitter: IBM Corporation

For other inquiries, please contact
webmaster@spec.org


Benchmark run on Tue Jun 10 17:01:07 EDT 2003 by SPECjAppServer2002 v1.14

Result submitted on Wed Jun 11 03:03:01 EDT 2003

Report generated by SPECjAppServer2002 Reporter v1.01


Copyright © 2002 Standard Performance Evaluation Corporation