SPECjAppServer®2004 Result Copyright © 2004 Standard Performance Evaluation Corporation |
Oracle Application Server 10g Release 10.1.3.3 - Java Edition on Sun SPARC Enterprise T5220 |
|
Submitter: Sun Microsystems Inc. |
SPEC license # 6 | Test date: Sep-2007 |
SUT Configuration | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
Benchmark Settings | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
Oracle Application Server 10g Release 10.1.3.3 - Java Edition | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Java HotSpot(TM) 32-Bit Server VM on Solaris, version 1.6.0_03 | ||||||
---|---|---|---|---|---|---|
|
Oracle JDBC Driver 10.2.0.3 (Thin) | ||||||
---|---|---|---|---|---|---|
|
Oracle Database Enterprise Edition Release 10.2.0.3 | ||||||
---|---|---|---|---|---|---|
|
J2EE Application Server | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
Emulator SW Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Database SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver SW Config - Primary | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver SW Config - Satellites 2 & 3 | ||||||
---|---|---|---|---|---|---|
|
||||||
|
J2EE AppServer HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Driver HW Primary (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Driver HW Emulator & Satellites (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 and M_WORKORDER 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_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 (ms) in orders-toplink-ejb-jar.xml deployment descriptor |
Durability Requirement Info:
To ensure database durability, RAID 1 (mirror disks) was used for the database files and logs maintained on the two Sun StorageTek 2540 Arrays. Each application server used a pair of mirrored disks in the Sun StorageTek 2540 array to provide durability for all the server logs and filestore for JMS persistence. |
Storage Requirement Info:
An 80 minute run at an injection rate of 1200 increased storage by 2190 MB This extrapolates to 39.42 GB storage for a 24 hour run. The database is configured with 3504 GB of storage. One Sun StorageTek 2540 FC Array was configured as a single RAID 1 logical drive to store the database files. The other Sun StorageTek 2540 FC Array was configure as two RAID 1 logical drives - one logical drive for the database logs and the other logical drive used for the application server JMS persistence logs |
Argument Passing Semantics:
Oracle Application Server 10g uses pass-by-value as required by the EJB Specification |
Bill of Materials |
---|
Supplier Description Product No. Qty -------- ------------------------------------------ ------------------ --- Sun SPARC Enterprise T5220, 1.4GHz, 8-core SEDAF121Z 1 Sun 4GB Memory Expansion (2x2GB) SESY2B1Z 8 Sun 73GB 10K RPM 2.5" SAS Disk SESY3A11Z 2 Sun 10 GbE XAUI card - Fiber SESY7XA1Z 1 Sun Transceiver for XAUI - 10GbE SR XFP SESY7XT1Z 1 Sun 4 Gb PCI-E Dual Port FC/AL card SG-XPCIE1FC-EM4 1 Sun DVD, 8X, RW SESY9DV1Z 1 Sun SE T5220 AC Power Supply SEDY9PS31Z 1 Sun Solaris 10 8/07 Preinstalled SESY9SA1Z 1 Sun SunSpectrum Upgrade: 3YGOLD, 24x7 W9D-T5220-8-24-3G 1 Sun SPARC Enterprise T5120, 1.2GHz, 8-core SECAC111Z 1 Sun 8GB Memory Expansion (2x4GB) SESY2C1Z 8 Sun 73GB 10K RPM 2.5" SAS Disk SESY3A11Z 2 Sun 10 GbE XAUI card - Fiber SESY7XA1Z 1 Sun Transceiver for XAUI - 10GbE SR XFP SESY7XT1Z 1 Sun 4 Gb PCI-E Dual Port FC/AL card SG-XPCIE1FC-EM4 1 Sun DVD, 8X, RW SESY9DV1Z 1 Sun SE T5120 AC Power Supply SECY9PS11Z 1 Sun Solaris 10 8/07 Preinstalled SESY9SA1Z 1 Sun SunSpectrum Upgrade: 3YGOLD, 24x7 W9D-T5120-8-24-3G 1 Sun Sun StorageTek 2540, 12 x 146GB, 2 RAID XTA2540R01D2E1752 2 Sun SunSpectum Upgrade: 3Y GOLD, 24x7 W9D-SE2540-24-3G 2 Sun 17" Entry Color Monitor X7204A 1 Sun XVR-200 Graphics Accelerator X3777 2 Sun USB Keyboard & Mouse 320-1366 1 Oracle Oracle Database 10g Release 2 Enterprise Edition, Per Processor 6** (v10.2) Oracle Partitioning, Per Processor, Unlimited users for 3 years 6** Oracle Oracle Database Server Support Package for 3 years 1 (Incident Server Support) 24x7x4 Oracle Oracle Application Server 10g Release 10.1.3.3, 6** Java Edition, Per Processor (v10.1) Oracle Oracle Application Server Support Package for 3 years 1 (Incident Server Support) 24x7x4 (** 6 = 0.75 * 8). Explanation: For the purposes of counting the number of processors which require licensing, a multicore chip with "n" cores shall be determined by multiplying "n" cores by a factor of .75). |
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 the 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://ecapps: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 log files were those that are normally 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.3 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. 10 GbE Switch Details: Foundry EdgeIron 8-port 10GbE Switch - Product No. EIF8X10G 5x 10GbE XFP Transceivers - Product No. 10G-XFP-SR |
For questions about this result, please contact the submitter: Sun Microsystems Inc. For other inquiries, please contact webmaster@spec.org
Copyright © 2004 Standard Performance Evaluation Corporation
First published at SPEC.org on 11-Oct-2007