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 rx2660 |
|
| Submitter: HP |
SPEC license # 3 | Test date: Jan-2007 |
| 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.05) 32 bit | ||||||
|---|---|---|---|---|---|---|
|
| Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.05) 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) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Load Driver and 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:
Data and redo logs were written to RAID 1 volume to provide durability. 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 488 increased storage by 1026 MB This extrapolates to 22GB of storage for a 24 hour run. The database is configured with over 500GB 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 Product # Qty
-------- ------------------------------------------- ---------------- ---
HP HP rx2660 1.6GHz/18MB 4-core AD245A-003 2
HP rx2660 PCI-X 3 slot cage option AD246A 2
HP 4GB DDR2 memory pair (2 x 2GB DIMMs) AD275A 2
HP 8GB DDR2 memory pair (2 x 4GB DIMMs) AD276A 4
HP 36GB 10K RPM drives AD140A 6
HP Dual port 1000BaseT LAN adapter card A7012A 2
HP Dual Port 4Gb Fibre Channel Adapter AB379A 2
HP HP-UX Integrity FOE w/Sys 2 Proc PCL LTU B9430AC 8
HP 3 year 24x7 hardware and software support HA110A3
HP Modular SAN Array 1000 201723-B22 2
HP 72GB 15K U320 Pluggable Hard Drive 286778-B22 28
HP 3 year 24x7 support HA110A3
Oracle Oracle Database 10g Release 2 Enterprise Edition, 2*
Partitioning, Per Processor
Oracle Oracle Database Server Support Package for 3 years 1
Incident Server Support -(24x7x4)
Oracle Oracle Application Server 10g - Java Edition, Per Processor 2*
(v10.1)
Oracle Oracle Application Server Support Package for 3 years 1
- Incident Server Support -Package - (24x7x4)
(* 2 = 0.50 * 4. 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. DNS server was used to load balance requests across the 2 network interfaces on the Appserver. 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. 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. |
For questions about this result, please contact the submitter: HP
For other inquiries, please contact
webmaster@spec.org
Copyright © 2004 Standard Performance Evaluation Corporation
First published at SPEC.org on 15-Feb-2007
