Copyright © 2004 Standard Performance Evaluation Corporation
|
|
SPECjAppServer®2004 Result Copyright © 2004 Standard Performance Evaluation Corporation |
| Oracle Application Server 10g Release 10.1.3.2 - Java Edition on HP-UX rx3600 Cluster |
|
| Submitter: Oracle Corporation |
SPEC license # 73 | Test date: Nov-2006 |
| SUT Configuration | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
| Benchmark Settings | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Detailed Results | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
| Oracle Application Server 10g Release 10.1.3.2 - Java Edition | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.03) 32 bit | ||||||
|---|---|---|---|---|---|---|
|
| Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.03) 64 bit | ||||||
|---|---|---|---|---|---|---|
|
| Oracle JDBC Driver 10.2.0.2 (Thin) | ||||||
|---|---|---|---|---|---|---|
|
| Oracle Database 10g Enterprise Edition Release 10.2.0.2 with patch 5339853 | ||||||
|---|---|---|---|---|---|---|
|
| J2EE Application Servers | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
| Emulator SW Config | ||||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
|
| Database SW Config | ||||||
|---|---|---|---|---|---|---|
|
||||||
|
| Driver SW Config Primary | ||||||
|---|---|---|---|---|---|---|
|
||||||
|
| J2EE AppServer HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Primary Load Driver and Satellites #1-#5 HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Satellite #6-#7 HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Emulator HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Benchmark Modifications |
|---|
Schema Modifications:
Tablespace sizes were increased to support the Injection rate. Scripts to create the DB are included in the FDA. Table and index initrans were modified. The M_INVENTORY, M_WORKORDER, M_PARTS, O_ORDERLINE tables were horizontally partitioned. Automatic segment space management was used for all tablespaces. System managed undo was used. Table locks were disabled during the run using disable_lock.sql |
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 (ms) in orders-toplink-ejb-jar.xml deployment descriptor. |
Durability Requirement Info:
To ensure database durability, RAID 1 (mirroring) was used for the database Redo logs. Data was laid out on RAID 0 and redolog files were sized to avoid log rollover for the duration of the run. The application server was using mirrored disks to provide durability for server logs and JMS persistence filestore. |
Storage Requirement Info:
An 80 minute run at an injection rate of 4100 increased storage by 10136 MB This extrapolates to 189GB of storage for a 24 hour run. The database is configured with 5697GB of storage. |
Argument Passing Semantics:
Oracle Application Server 10g uses pass-by-value as required by the EJB specification. |
| Bill of Materials |
|---|
Supplier Description Product # Qty
-------- ------------------------------------------- ---------------- ---
HP HP rx3600 1.6GHz/18MB 4-core AB596A-160 11
HP 4GB memory using 1GB DIMMS AB564A-0D1 44
HP 36GB 10K RPM drives AD140A-0D1 33
HP iether 2 port Gigabit LAN card A7012A-0D1 22
HP 4Gb Dual Port Fibre Channel Adapter AB379A 11
HP HP-UX 11iV2 FOE B9430AC 44
HP 3 year 24x7 hardware and software support HA110A3
HP HP Superdome Server Solution A5200A 1
HP 32 processor Superdome Enterprise Server A9834A-429 1
HP 200-240VAC 3 phase, 4 wires, 8 gage cord A9834A-006 1
HP Superdome sx2000 Cell Board for Montecito A9837A-0D1 8
HP 1.6 GHz Montecito with 24MB cache A9840A-0D1 32
Itanium dual-core module
HP Memory - 16GB high performance DDR2 A9846A-0D1 32
(8x2GB DIMM)
HP HP 12 Slot PCI-X Chassis for sx2000 A9836A-0D1 4
HP 2Gb PCI-X DC 64 bit FC HBA A6826A-0D1 8
HP PCI-X 2 port 1000Base-T Gigabit Adptr A7012A-0D1 8
HP HP-UX OE LTU B9429CA-UMG,0D1,AJR 32
HP HP rx2620 1.0G 1.5MB CPU server Solution AB332A 1
Admin Console
HP HP 3y 4h 24x7 HW SW Support HA110A3 1
HP Modular SAN Array 1000 201723-B22 9
HP 72GB 15K U320 Pluggable Hard Drive 286778-B22 120
HP MSA Controller 218231-B22 9
HP MSA 1000 Fibre Channel IO Module 218960-B21 9
HP 256MB Cache Module 254786-B21 9
HP 3 year 24x7 support HA110A3
HP ProCurve 2848 Switch J4904A 2
HP 3 year 24x7 support HA110A3
Oracle Oracle Database 10g Release 2 Enterprise Edition, 32*
Partitioning, Per Processor
(v10.2)
Oracle Oracle Database Server Support Package for 3 years 1
Incident Server Support -(24x7x4)
Oracle Oracle Application Server 10g - Java Edition, Per Processor 22*
(v10.1)
Oracle Oracle Application Server Support Package for 3 years 11
- Incident Server Support -Package - (24x7x4)
(* 32 = 0.50 * 64) & (22= 0.50*44). 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 sent to different Appservers 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.specj.com:23791/SPECjAppServer java.naming.security.principal=oc4jadmin java.naming.security.credentials=welcome oracle.j2ee.rmi.loadBalance=lookup |
| General Notes |
|---|
The only errors in the driver error logs are the application errors generated by this benchmark. Two Database checkpoints during the Measurement Interval were done by using the Oracle SQLPlus command: alter system checkpoint Oracle Application Server 10g Release 10.1.3.2 implements Recoverable Last Resource Commit (RLRC) 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. In conjunction with the RLRC implementation, the log-file location specified in the transaction-manager.xml identifies the location where the participating resource managers are recorded. The commit record table name associated with an instance is specified in the commit-record-table-name attribute, in the Connection-Factory element of data-sources.xml. |
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 06-Dec-2006
