SPECjAppServer2002 Result Copyright © 2002 Standard Performance Evaluation Corporation |
Oracle Application Server 10g Java Edition v9.0.4.0.1p1 on Fujitsu-Siemens PRIMEPOWER 450 |
|
Submitter: Oracle Corporation |
SPEC license # 73 | Test date: Aug- 2004 |
EJB Container Avail: Nov-2004 EJB Container JVM Avail: Aug-2004 |
Benchmark Settings | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | |||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||
|
EJB Container | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||
|
Supplier Domain Container | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||
|
Emulator Container | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||
|
Database | ||||||
---|---|---|---|---|---|---|
|
||||||
|
JDBC | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Other Software | ||||||
---|---|---|---|---|---|---|
|
||||||
|
J2EE Application Server (9 systems) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Database Server (1 system) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Driver (Master) (1 system) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Driver (Satellite) (1 system) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Emulator (1 system) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Benchmark Modifications |
---|
Schema Modifications:
Tablespace sizes were increased to support the Injection rate. Scripts to create the DB are included in the FDA. Two indexes were created on the M_largeorder table: CREATE UNIQUE INDEX M_lo_idx ON M_largeorder (lo_id) CREATE UNIQUE INDEX M_OL_O_idx ON M_largeorder (lo_o_id, lo_ol_id) Table and index initrans, pctfree, pctused parameters were modified. Automatic segment space management was used for tablespaces. M_WORKORDER, O_ORDERS, O_ORDERLINE,M_INVENTORY, C_CUSTOMER tables were horizontally partitioned. Field width of pol_balance was changed to (11, 2) from (9, 2). System managed undo was used. Table locks were disabled during the run using tbllkd.sh. |
Load Program Modifications:
The load program was not modified |
Reference Bean Modifications:
No changes were made to the reference beans |
Benchmark Configuration Information |
---|
Persistence Mode Used:
CMP mode was used for all beans |
Isolation Requirement Info:
Beans with a READ_COMMITTED requirement were deployed using locking-mode="optimistic" in their deployment descriptors All other beans were deployed using locking-mode="pessimistic Pessimistic locking mode means that all selects (including finders) are issued with a FOR UPDATE clause in the select statement |
Durability Requirement Info:
RAID 10 was used for Redo logs for durability. The database writes all changes to the redo log when each transaction is committed. Two battery backed FibreCat S80 storage arrays (12 X 73Gb) were used to store the data and logfiles. One for data and One for logfiles. Please see Notes section below. |
Storage Requirement Info:
A 45 minute run at an injection rate of 3475 required 61.34GB of storage. This extrapolates to 654.30GB of storage for an 8-hour run. The database system is configured with 1752GB of storage. |
Argument Passing Semantics:
Oracle Application Server 10g uses pass-by-value as required by the EJB specification |
Other Benchmark Information |
---|
This submission used the xerces.jar from the SPECjAppServer2002 kit. No hardware or software was used to alter basic network routing. Requests were sent to different appservers utilizing DNS round-robin with one of the mid-tier nodes acting as the DNS server. The driver used the following jndi.properties: java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory java.naming.provider.url=ormi://mtdns.bmc.all:23791/SPECjAppServer java.naming.security.principal=admin java.naming.security.credentials=welcome dedicated.rmicontext=true |
General Notes |
---|
No errors were reported during the final nor reproducability run. The SUT contained 73 GB disks for both redo logs and data; however, subsequent calculation indicated that 146 GB disks would have been required to hold the redo generated during an 8 hour run. To comply with this benchmark requirement, for pricing purposes 146 GB disks were substituted for 73 GB disks for redo logs only as per Clause 4.3 of the run rules; this substitution is performance neutral. |
For questions about this result, please contact the submitter: Oracle Corporation For other inquiries, please contact webmaster@spec.org
Benchmark run on Tue Aug 17 23:30:50 CEST 2004 by SPECjAppServer2002 v1.14
Result submitted on null
Report generated by SPECjAppServer2002 Reporter v1.01
Copyright © 2002 Standard Performance Evaluation Corporation
First published at SPEC.org on 03-Sep-2004