SPECjAppServer®2004 Result Copyright © 2004 Standard Performance Evaluation Corporation |
Oracle Application Server 10g Release 10.1.3.3.2 - Java Edition on HP-UX Integrity BL870c Server Blade Cluster |
|
Submitter: Oracle Corporation |
SPEC license # 73 | Test date: Aug-2008 |
SUT Configuration | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
Benchmark Settings | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
Oracle Application Server 10g Release 10.1.3.3.2 - Java Edition | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.14) 64 bit | ||||||
---|---|---|---|---|---|---|
|
Java HotSpot(TM) 64-Bit Server VM on Linux, version 1.6.0_06 | ||||||
---|---|---|---|---|---|---|
|
Oracle JDBC Driver 10.2.0.3 (Thin) | ||||||
---|---|---|---|---|---|---|
|
Oracle Database 11g Enterprise Edition Release 11.1.0.6 with patch for 7254300 | ||||||
---|---|---|---|---|---|---|
|
J2EE Application Servers | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
Emulator SW Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Database SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver SW Config Primary and Satellites | ||||||
---|---|---|---|---|---|---|
|
||||||
|
J2EE AppServer HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Primary Load Driver, Satellite Drivers #1-#14 and Emulator (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
DNS Load Balancer Hardware (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 C_CUSTOMER, C_CUSTOMERINVENTORY, M_INVENTORY, M_WORKORDER, O_ORDERLINE, O_ORDERS, S_COMPONENT, S_PURCHASEORDER and S_PURCHASEORDERLINE tables were horizontally partitioned. M_PARTS and M_BOM were hash clustered. 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 and datafiles. The application server was using mirrored disks to provide durability for server logs and JMS persistence filestore. The RAID controller on the database and application server machines were configured with Write-Back cache policy supported with battery backed up unit on the controller. |
Storage Requirement Info:
An 80 minute run at an injection rate of 10,300 increased storage by 32.0 GB This extrapolates to 504GB of storage for a 24 hour run. The database is configured with 16TB 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 Integrity BL870c Blade Server AH232A 12 HP 1.60GHz 24MB Itanium Processors AH320A 48 HP 4GB (2 x 2GB) PC2-4200 DDR2 SDRAM DIMMs AD344A 144 HP 146GB SAS 10,000rpm disk drive 418367-B21 24 HP QLogic QMH2462 4Gb FC HBA 403619-B21 12 HP C7000 Enclosure AD361B 3 HP 4Gb Fibre Channel Pass-thru Module 403626-B21 3 HP 1Gb Ethernet Pass-Thru Module 406740-B21 6 HP BladeSystem c7000 Active Cool Fan 412140-B21 30 HP BladeSystem c7000 Power Module 413379-B21 18 HP HP-UX FOE BA531AC 48 HP 3 year 24x7 hardware and software support HA110A3 HP HP Superdome Server Solution A5200A 2 HP 32 processor Superdome Enterprise Server A9834A-429 2 HP 200-240VAC 3 phase, 4 wires, 8 gage cord A9834A-006 2 HP Superdome sx2000 Cell Board for Montecito A9837A-0D1 14 HP 1.6GHz 24MB Itanium 2 9000 A9840A-0D1 56 Itanium dual-core module HP Memory - 16GB high performance DDR2 A9846A-0D1 28 (8x2GB DIMM) HP HP 12 Slot PCI-X Chassis for sx2000 A9836A-0D1 6 HP 4Gb PCI-X DC 64 bit FC HBA A6826A-0D1 16 HP PCI-X 2 port 1000Base-T Gigabit Adptr A7012A-0D1 7 HP HP-UX OE LTU B9429CA-UMG,0D1,AJR 56 HP HP rx2620 1.0G 1.5MB CPU server Solution AB332A 1 Admin console HP 3y 24x7 HW SW Support HA110A3 HP EVA8100 2C6D Array AG701A 4 HP StorageWorks 4/16 Full SAN Switch AG757A 4 HP CV EVA 8k Series Unlimited Lic T5183A 4 HP M5314C FC Drive Enclosure AD542C 8 HP StorageWorks 146GB 15K FC HDD 364621-B23 448 HP 4GB SW Single Pack SFP Transceiver A7446B 64 HP Storage Works LC/LC 2m Cable 221692-B21 54 HP 24A High Voltage US/JP Modular PDU 252663-D72 8 HP Universal Rack 10642 G2 Shock Rack AF002A 4 HP 10K G2 600W Stabilizer Kit AF062A 4 HP 10642 G2 Sidepanel Kit AF054A 4 HP CV EVA 7.0 Rep Sol Mgr 3.0 Media Kit T3724E 1 HP Stor Essen Std Ed SRM Media Kit T5314AA 1 HP Stor Essen Std Ed SRM LTU T5315AA 1 HP 3y Proactive 24 Service HA111A 4 HP EVA 6100 - Model 2C4D Base AD556C 1 2 x HSV200-B controllers 4 x M5314C Disk Enclosures HP StorageWorks 146GB 15K FC HDD 364621-B23 56 HP HP rx2660 1.6GHz/18MB 4-core AD245A-003 3 HP rx2660 PCI-X 3 slot cage option AD246A 3 HP 4GB DDR2 memory pair (2 x 2GB DIMMs) AD275A 12 HP 36GB 10K RPM drives AD140A 3 HP Dual port 1000BaseT LAN adapter card A7012A 3 HP HP-UX Integrity FOE w/Sys 2 Proc PCL LTU B9430AC 12 HP 3 year 24x7 hardware and software support HA110A3 HP HP ProCurve 5304xl Switch 24 Port Module J8702-61001 3 Oracle Oracle Database 11g Enterprise Edition, 56* Per Processor, Unlimited Users for 3 years Oracle Partitioning, Per Processor, Unlimited Users for 3 years 56* Oracle Oracle Database Server Support Package for 3 years 1 Incident Server Support -(24x7x4) Oracle Oracle Application Server 10g - Java Edition, Per Processor 48* Oracle Oracle Application Server Support Package for 3 years 12 - Incident Server Support -Package - (24x7x4) (* 56 = 0.50 * 112) & (48= 0.50*96). 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 DNS servers running on the DNS load balancer hardware. 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 and those caused by network contention during the benchmark's initial ramp up period. 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.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: Oracle Corporation For other inquiries, please contact webmaster@spec.org
Copyright © 2004 Standard Performance Evaluation Corporation
First published at SPEC.org on 10-Sep-2008