Copyright © 2004 Standard Performance Evaluation Corporation
|
|
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 BL860c Server Blade Cluster |
|
| Submitter: Oracle Corporation |
SPEC license # 73 | Test date: Nov-2007 |
| 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.08) 32 bit | ||||||
|---|---|---|---|---|---|---|
|
| Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.08) 64 bit | ||||||
|---|---|---|---|---|---|---|
|
| Oracle JDBC Driver 10.2.0.3 (Thin) | ||||||
|---|---|---|---|---|---|---|
|
| Oracle Database 10g Enterprise Edition Release 10.2.0.3 with Oracle Real Application Clusters Option and patch 5500535 | ||||||
|---|---|---|---|---|---|---|
|
| J2EE Application Servers | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
| Emulator SW Config | ||||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
|
| Database SW Config - RAC Node 1 | ||||||
|---|---|---|---|---|---|---|
|
||||||
|
| Database SW Config - RAC Node 2 | ||||||
|---|---|---|---|---|---|---|
|
||||||
|
| Driver SW Config Primary and Satellites | ||||||
|---|---|---|---|---|---|---|
|
||||||
|
| J2EE AppServer HW (SUT hardware) (SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Database Server HW (SUT hardware) (SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Primary Load Driver and Satellite Drivers (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Emulator HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| DNS Load Balancer Hardware (SUT 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 M_INVENTORY, M_WORKORDER, M_PARTS, O_ORDERLINE, S_SUPP_COMPONENT, S_PO, C_CUSTOMERINVENTORY, O_ORDERS 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 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 5700 increased storage by 13.76GB This extrapolates to 248GB 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 BL860c blade server AD323A-006 11
2 x 1.67GHz Itanium 9100 processors
HP 4GB (2 x 2GB) PC2-4200 DDR2 SDRAM DIMMs AD344A 66
HP 72GB SAS 15,000rpm disk drive 431935-B21 11
HP QLogic QMH2462 4Gb FC HBA 403619-B21 11
HP C7000 Enclosure AD361B 2
HP 4Gb Fibre Channel Pass-thru Module 403626-B21 4
HP 1Gb Ethernet Pass-Thru Module 406740-B21 4
HP BladeSystem c7000 Active Cool Fan 412140-B21 11
HP BladeSystem c7000 Power Module 413379-B21 11
HP HP-UX FOE BA531AC 44
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 10
HP 1.6 GHz Montecito with 24MB cache A9840A-0D1 40
Itanium dual-core module
HP Memory - 16GB high performance DDR2 A9846A-0D1 20
(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 8
HP PCI-X 2 port 1000Base-T Gigabit Adptr A7012A-0D1 8
HP HP-UX OE LTU B9429CA-UMG,0D1,AJR 40
HP HP rx2620 1.0G 1.5MB CPU server Solution AB332A 1
Admin Console
HP 3 year 24x7 hardware and software support HA110A3
HP HP ProCurve 2848 Switch J4904A 1
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 MSA Controller 218231-B22 2
HP MSA 1000 Fibre Channel IO Module 218960-B21 2
HP 256MB Cache Module 254786-B21 2
HP 3 year 24x7 hardware and software support HA110A3
HP EVA810 2C6D Array AG701A 2
HP StorageWorks 4/32 Full SAN Switch AG757A 2
HP CV EVA 8k Series Unlimited Lic T5183A 2
HP M5314C FC Drive Enclosure AD542C 8
HP StorageWorks 146GB 15K FC HDD 364621-B23 224
HP 4GB SW Single Pack SFP Transceiver A7446B 32
HP Storage Works LC/LC 2m Cable 221692-B21 32
HP 24A High Voltage US/JP Modular PDU 252663-D72 4
HP Universal Rack 10642 G2 Shock Rack AF002A 1
HP 10K G2 600W Stabilizer Kit AF062A 1
HP 10642 G2 Sidepanel Kit AF054A 1
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 Bus Copy EVA8K Ser 1TB LTU T5341A 1
HP 3y Proactive 24 Service HA111A3
HP HP rx3600 1.6GHz/18MB 4-core AB596A-160 1
HP 8GB memory using 2GB DIMMS AB565A-0D1 4
HP 36GB 10K RPM drives AD140A-0D1 1
HP iether 2 port Gigabit LAN card A7012A-0D1 1
HP 4Gb Dual Port Fibre Channel Adapter AB379A 1
HP HP-UX FOE B9430AC 4
HP 3 year 24x7 hardware and software support HA110A3
Oracle Oracle Database 10g Release 2 Enterprise Edition, 40*
Per Processor (v10.2)
Oracle Partitioning, Per Processor, Unlimited Users for 3 years 40*
Oracle Real Application Cluster, Per Processor, 40*
Unlimited Users for 3 years
Oracle Oracle Database Server Support Package for 3 years 2
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)
(* 40 = 0.50 * 80) & (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 a DNS server running on the DNS load balancer node. 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 Real Application Clusters (RAC) is an option to Oracle Database 10g Enterprise edition. RAC extends Oracle Database so that you can store, update, and efficiently retrieve data from multiple instances on different servers at the same time. Oracle RAC provides the software that allows the servers to work together in what is called a cluster. The physical structures that make up the database must reside on shared storage that is accessible from all servers that are part of the cluster. Each server in the cluster runs the Oracle RAC software. Single-instance Oracle databases have a one-to-one relationship between datafiles and the instance. Oracle RAC environments, however, have a one-to-many relationship between datafiles and instances. In Oracle RAC environments, multiple cluster database instances form a single database. The instances can be on different servers, referred to as hosts or nodes. Each cluster database instance in an Oracle RAC cluster uses its own memory structures and background processes. Oracle RAC uses Cache Fusion to synchronize the data stored in the buffer cache of each cluster database instance. When a data block located in the buffer cache of one instance is required by another instance, Cache Fusion transfers the data block directly between the instances using the interconnect, enabling the Oracle RAC database to access and modify data as if the data resided in a single buffer cache. Oracle RAC uses Oracle ASM (Automatic Storage Management) to manage storage shared between the RAC instances. The Volume groups / Raw partitions of disks can be presented to ASM for creating Data and log file stores. 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 21-Nov-2007
