Copyright © 2004 Standard Performance Evaluation Corporation
|
|
SPECjAppServer®2004 Result Copyright © 2004 Standard Performance Evaluation Corporation |
| BEA WebLogic Server 9.2 on Fujitsu SPARC Enterprise T2000 |
|
| Submitter: Fujitsu Limited |
SPEC license # 19 | Test date: Dec-2006 |
| SUT Configuration | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
| Benchmark Settings | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Detailed Results | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
| BEA WebLogic Server 9.2, Advantage Edition | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 10 32-bit | ||||||
|---|---|---|---|---|---|---|
|
| Java (TM) 2 Platform Standard Edition Development Kit 5.0 Update 6 32-bit | ||||||
|---|---|---|---|---|---|---|
|
| IBM DB2 Universal JDBC Drivers | ||||||
|---|---|---|---|---|---|---|
|
| IBM DB2 Universal Database v8.2.6 (64-bit) | ||||||
|---|---|---|---|---|---|---|
|
| J2EE Application Server | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
| Emulator SW Config | ||||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
|
| Database SW Config | ||||||
|---|---|---|---|---|---|---|
|
||||||
|
| Driver SW Config Primary & Satellite 1 | ||||||
|---|---|---|---|---|---|---|
|
||||||
|
| Driver SW Config Satellite 2 | ||||||
|---|---|---|---|---|---|---|
|
||||||
|
| J2EE AppServer HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Load Driver HW Primary/Emulator & Satellite 1 (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Load Driver HW Satellite 2 (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. |
Load Program Modifications:
The load program was not modified |
| Benchmark Configuration Information |
|---|
Isolation Requirement Info:
The following beans: PartEnt, ComponentEnt, AssemblyEnt, BomEnt and LargeOrderEnt in the Manufacturing Domain, ItemEnt in the Orders Domain, and SupplierCompEnt and SupplierEnt in the Supplier Domain were accessed using READ_COMMITTED which is Cursor Stability (CS) for DB2. The remaining beans were accessed using REPEATABLE_READ which translates to DB2 isolation level of Read Stability (RS) The ItemEnt bean was cached for 15 minute intervals by setting concurrency-strategy to ReadOnly read-timeout-seconds to 900 in bea-orders.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 StorEdge 3320 Arrays. The application server has a pair of mirrored disks (using the Solaris Volume Manager) 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 482 increased storage by 366 MB This extrapolates to 6.5 GB storage for a 24 hour run. The database is configured with 1752 GB of storage. Each Sun StorEdge 3320 SCSI Array was configured with a single RAID 1 logical drive. |
Argument Passing Semantics:
BEA WebLogic 9.2 uses pass-by-value as required by the EJB Specification. |
| Bill of Materials |
|---|
Supplier Description Product No. Qty
-------- ------------------------------------------ ------------------ ---
Fujitsu Fujitsu SPARC Enterprise T2000, 1.4 GHz T1 SEBPJMC1U 1
64GB,2x73GB SCSI
Fujitsu 73GB 10K RPM 2.5" SAS Disk SEPX3A11U 2
Sun Solaris 10 11/06 Media SOLZ9-10FC9A7M 1
Sun Sun Fire T2000,1.0 GHz T1,8GB,2x73GB SCSI T20Z106A-08GA2D 1
Sun Solaris 10 6/06 Media SOLZ9-10EC9A7M 1
Sun Ultra320 SCSI Dual Channel Adapter SGXPCI2SCSILM320-Z 1
Sun SunSpectrum Upgrade: 3YGOLD, 24x7 W9D-T2000-6-24-3G 1
Sun Sun StorEdge 3320, 12 x 73 GB, 1 RAID XTA3320R01A1T876 2
Sun SunSpectum Upgrade: 3Y GOLD, 24x7 W9D-SE3320-24-3G 2
Sun 17" Entry Color Monitor X7204A 1
Sun XVR-200 Graphics Accelerator X3777 2
Sun USB Keyboard 320-1271 1
Sun USB Mouse 320-2632 1
BEA BEA WebLogic Server 9.2 License, Advantage Edition 1
for 8-core CPU
BEA 3-year 24x7x4 Support for WebLogic Server 1
IBM DB2 UDB ENTERPRISE SERVER EDITION PROCESSOR D54PYLL 1.8
LIC+SW MAINT 12 MO
IBM DB2 UDB ENTERPRISE SERVER EDITION PROCESSOR E01MXLL 3.6
SW MAINT RNWL 1 ANNIV
|
| Other Benchmark Information |
|---|
This submission used the xerces implementation 2.6.2 provided with WebLogic 9.2. |
| General Notes |
|---|
This result was measured on the Sun Fire T2000. The Fujitsu SPARC Enterprise T2000 and Sun Fire T2000 are electronically equivalent. The only errors in the driver log files were those that are normally generated by this benchmark. DB2 uses "Soft" checkpoint to ensure that no updates remain unflushed for longer than the allowed time. When DB2 UDB Server changes a database table with an update, insert, or delete operation, the change is initially made in memory, not on disk. When there is not enough space in the memory buffer to read in or write additional data pages, DB2 UDB Server will make space by flushing some modified pages to disk. Modified pages are also written to disk as part of the "Soft" checkpoint to ensure that no updates remain unflushed for longer than the allowed time. Before a change is made to the database, it is first recorded in the transaction log. This ensures that the database can be recovered completely in the event of a failure. Using the transaction log, transactions that started but did not complete prior to a failure can be undone, and transactions recorded as complete in the transaction log but not yet written to disk can be redone. DB2 UDB uses a write-ahead-logging protocol to guarantee recovery. This protocol uses "Soft" checkpoint to write least-recently-used database to disk independent of transaction commit. However, enough log information to redo/undo the change to a database pages is committed to disk before the database page itself is written. This protocol therefore renders checkpoint unnecessary for DB2 UDB. |
For questions about this result, please contact the submitter: Fujitsu Limited For other inquiries, please contact webmaster@spec.org
Copyright © 2004 Standard Performance Evaluation Corporation
First published at SPEC.org on 17-Apr-2007
