SPECjAppServer®2004 Result Copyright © 2004 Standard Performance Evaluation Corporation |
Oracle Application Server 10G Release 10.1.3.2 - Java Edition on Rackable Systems C2002 |
|
Submitter: Oracle Corporation |
SPEC license # 73 | Test date: Aug-2007 |
SUT Configuration | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
Benchmark Settings | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
Oracle Application Server 10G Release 10.1.3.2 - Java Edition | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
BEA JRockit(R) 6.0 JDK (R27.3.0-106) (Linux x86 32bit) | ||||||
---|---|---|---|---|---|---|
|
Java (TM) 2 Platform Standard Edition Development Kit 6.0 Update 2 64-bit | ||||||
---|---|---|---|---|---|---|
|
Oracle JDBC Driver 10.2.0.2 (Thin) | ||||||
---|---|---|---|---|---|---|
|
Oracle Database Enterprise Edition Release 10.2.0.2 | ||||||
---|---|---|---|---|---|---|
|
J2EE Application Server | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
Emulator SW Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Database SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver SW Config Primary | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver SW Config Satellite | ||||||
---|---|---|---|---|---|---|
|
||||||
|
J2EE Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Drivers and Emulator HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Benchmark Modifications |
---|
Schema Modifications:
Tablespace sizes were increased to support the Injection rate. Table and index initrans were modified. The M_WORKORDER and O_ORDERLINE tables were horizontally partitioned. Scripts to create the DB are included in the FDA. Table locks were disabled during the run using disable_locks.sh script. |
Load Program Modifications:
The load program was not modified. |
Benchmark Configuration Information |
---|
Isolation Requirement Info:
The following Beans were deployed in READ_COMMITTED mode as per the benchmark requirement: Mfg - AssemblyEnt, BomEnt, ComponentEnt, LargeOrderEnt, PartEnt Orders - ItemEnt Supplier - SupplierCompEnt, SupplierEnt All other beans were deployed using pessimistic locking mode such that all selects including finders are issued with a FOR UPDATE clause in select statement: Corp - CustomerEnt, CustomerInventoryEnt Mfg - InventoryEnt, WorkOrderEnt Orders - OrderEnt, OrderLineEnt Supplier - POEnt, POLineEnt, SComponentEnt Util - SequenceEnt The ItemEnt bean was cached for 20 minute intervals by setting read-only to true and time-to-live to 1200000 in orders-toplink-ejb-jar.xml. |
Durability Requirement Info:
To ensure database durability, RAID 1 (mirroring) was used for the data files and database Redo logs. The application server was using mirrored disks to provide durability for server logs and JMS persistence filestore. The RAID controller on the database and the application server machines were configured with Write-Back cache policy supported with battery backup unit on the controller. |
Storage Requirement Info:
A 80 min run at Injection Rate of 1000 increased storage by 3 GB. Extrapolating for 24 hrs we need 54 GB. The system is configured with over 975 GB of durable storage. |
Argument Passing Semantics:
Oracle Application Server 10g uses pass-by-value as required by the EJB specification. |
Bill of Materials |
---|
Supplier Description SKU # Qty -------- ------------------------------------------- ---------------- --- Rackable Systems S3118 Storage System S3118-L03-X5345-AS-A 1 Rackable Systems C2002 Server C2002-L03-X5355-AS-A 1 Rackable Systems Platinum Support Coverage for 3 years 50-40-00003 2 Cisco Catalyst 3560G Switch 39-00-00177 1 Red Hat Enterprise Linux Premium Subscription (1 Year) 6 Oracle Oracle Database 10g Release 2 Enterprise Edition, Per Processor Unlimited Users for 3 years 4* Oracle Partitioning, Per Processor, Unlimited Users for 3 years 4* Oracle Oracle Database Server Support Package for 3 years (Incident Server Support) 24x7x4 1 Oracle Oracle Application Server 10g Release 10.1.3.2, Per Processor (v10.1) 4* Oracle Oracle Application Server Support Package for 3 years (Incident Server Support) 24x7x4 1 (* 4 = 0.50 * 8). Explanation: For the purposes of counting the number of processors which require licensing, an Intel multicore chip with "n" cores shall be determined by multiplying "n" cores by a factor of 0.50). |
Other Benchmark Information |
---|
The xerces implementation version 2.6.2 from xml.apache.org was used as it comes packaged with Oracle Application Server 10g. Requests were directed to the Appserver instances using DNS round robin, with the database node 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://main.spec.com:23791/SPECjAppServer java.naming.security.principal=oc4jadmin java.naming.security.credentials=welcome oracle.j2ee.rmi.loadBalance=lookup |
General Notes |
---|
On the database, incremental checkpointing ensured that no buffer will remain dirty (in the cache) for more than the allowed time. Oracle Application Server 10g Release 10.1.3.2 implements Recoverable Last Resource Commit optimization where one and only one SinglePhaseResource participates in a global transaction with one or more XAResources. This is accomplished by emulating an XAResource to represent the 1PC resource. The transaction manager takes the following steps when it receives a request to commit a global transaction that includes one emulated XAResource: 1. It invokes a prepare call on each of the 2PC resources. 2. If all of the 2PC resources are successfully prepared, then commit (one-phase) is called and the commit record is written to the commit-log, on the emulated XA resource (database) as part of the local transaction. 3. If the 1PC on the emulated XA resource completes successfully, then the transaction manager calls commit on each of the 2PC resources. or: If the 1PC on the emulated XA resource fails, then the transaction manager queries the commit-log for transaction outcome. If the record exists, 2PC resources are committed, otherwise 2PC Resources are aborted. Transaction outcome after a single point of failure is guaranteed by the presence of the commit-record in the commit log, indicating a successful transaction completion; while a missing commit-record signifies abort. The commit record is deleted lazily after the global transaction has committed. The only errors in the driver error logs are the application errors generated by this benchmark. |
For questions about this result, please contact the submitter: Oracle Corporation
For other inquiries, please contact
webmaster@spec.org
Copyright © 2004 Standard Performance Evaluation Corporation
First published at SPEC.org on 29-Aug-2007