SPECjAppServer®2004 Result Copyright © 2004 Standard Performance Evaluation Corporation |
WebSphere 6.1 Application Server on IBM System p 570 (4.7 GHz, 4 core) |
|
Submitter: IBM Corporation |
SPEC license # 11 | Test date: Aug-2007 |
SUT Configuration | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
Benchmark Settings | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
WebSphere Application Server V6.1 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0) | ||||||
---|---|---|---|---|---|---|
|
IBM DB2 Universal JDBC Drivers | ||||||
---|---|---|---|---|---|---|
|
IBM DB2 Universal Database 9.1 | ||||||
---|---|---|---|---|---|---|
|
J2EE Application Servers | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
Emulator SW Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Database SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Primary Driver SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Satellite Driver SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
J2EE Application Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Emulator (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Driver Primary and Satellite (non-SUT hardware) (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Benchmark Modifications |
---|
Schema Modifications:
No changes were made to the benchmark schema. |
Load Program Modifications:
No changes were made to the load program. |
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 20 minute intervals using the WebSphere Lifetime in Cache Mechanism. Only the data inside the bean was cached. |
Durability Requirement Info:
To ensure database durability, RAID5 was used for the database logs maintained on the external storage. The log device contains two 5+P arrays. A total of 12 x 36GB disks were used for the log. |
Storage Requirement Info:
Over the course of a 75 minute run at an injection rate of 716, the database storage for database system increased by 498 MB. Given a linear scale, a 24 hour run at the same injection rate would increase storage for database system by 9561 MB. Two RAID1 disk arrays were used to create the filesystem space for the database. Each array contained 8 x 36GB disks providing 131.6 GB of storage. The combined storage available for the database was 263 GB. |
Argument Passing Semantics:
WebSphere Application Server V6.1 uses pass-by-value semantics by default. |
Bill of Materials |
---|
IBM System p 570 WebSphere 6.1 with DB2 v9.1 Database Server Supplier IBM System p 570 WebSphere 6.1 Hardware (for one system) Product Description Qty -------- --------------------------------------------- --- 9117-MMA Server 1:9117 Model MMA 1 0265 AIX Partition Specify 1 1845 Operator Panel 1 3647 146 GB 15K RPM SAS Disk Drive 4 4650 Rack Indicator- Not Factory Integrated 1 5005 Software Preinstall 1 5403 One Processor Activation for Processor Feature #7380 4 5625 Proc Power Regulator 3 5626 System CEC Enclosure with Bezel 1 5628 Sys AC Power Supply, 1600 W 2 5629 Media Enclosure and Backplane 1 5636 Integrated, 2X- 1Gb Virtual Ethernet, I/O ports 1 5648 Service Interface Card 1 5663 Proc Enclosure and Backplane 1 5667 System Midplane 1 5668 SAS Disk Backplane -6 slot 1 5680 Activation of 1GB DDR2- P6 Memory 16 5694 0/8GB DDR2 Memory (4X2GB) DIMMS- 667 MHz-POWER6 Memory 4 5699 System Ship Group 1 5706 IDE Slimline DVD-ROM Drive 1 6671 Power Cord (9-foot), Drawer to IBM PDU, 250V/10A 2 7164 IBM Rack-mount Drawer Rail Kit 1 7380 4.7 GHz Proc Card, 0/2 Core POWER6, 12 DDR2 Memory Slots 2 7870 Power Midplane 1 9300 Language Group Specify - US English 1 Supplier IBM System p5 550 Database Hardware (for one system) Product Description Qty -------- ---------------------------------------------------- ----- 9133-55A Server 2:9133 Model 55A 1 1910 4 Gb Dual Port Fibre Channel 1 1931 2048MB (2x1024MB) DIMMs, 276-pin, 4 1968 73.4 GB 10,000 RPM Ultra320 SCSI Disk Drive 1 1994 IDE Slimline DVD-ROM Drive 1 6592 4-Disk Slot Exp - Base Ctlr 1 7286 One Processor Activation for Processor Feature #8286 4 7876 CPU Power Regulator 2 7877 Media Backplane Card 1 8286 2-core 2.1 GHz POWER5+ Processor Card, 36MB L3 2 1812-81A DS4000 EXP810 Expansion Unit Model 81 2 5231 (40K6800) 2 Gbps FC, 36.4 GB/15K E-DDM 14 1814-70A DS4700 Express Model 70 (2 GB Cache) 2 5231 (40K6800) 2 Gbps FC, 36.4 GB/15K E-DDM 14 5605 (19K1248) Fiber Cable 5m Multimode (LC-LC) 4 7382 (41Y5222) DS4700 Mod 70 EXPs Att. 1-3 2 7711 (41Y5184) DS4700 AIX Host Kit 2 8850 DS4700 Mod 70 2-Storage Partitions Activation 2 570 3 year support, 24x7x4 1 Supplier Miscellaneous Hardware Product Description Qty -------- ----------------------------------------------------- ----- 7310-C03 HMC 1:7310-C03 Desktop Hardw.Mgmt.Console 1 8800 Quiet Touch Keyboard - USB, Business Black 1 8841 Mouse - Business Black with Keyboard Attachment Cable 1 3631 IBM C117 17" CRT Monitor 1 0569 HMC Support, 3 year, 24x7x4 1 497268 Cisco 3750-24-TS 1 150984 Cisco Support 1 year, 24x7x4 1 Supplier Passport Advantage Software Product Description Qty -------- ------------------------------------------------------------------ ----- D51NDLL DB2 UDB Enterprise Server Edition Processor Lic+SW Maint 12 Months 2 E00BILL DB2 UDB Enterprise Server Edition Processor SW Maint Rewl 1 Anniv 2 D5CB9LL IBM WebSphere Application Server Processor Lic+SW Maint 12 Months 2 E1CBBLL IBM WebSphere Application Server SW Maintenance 12 Months 2 Supplier Operating System Software Product Description Qty -------- ------------------------------------------------------------------ ----- 5692-A5L IBM AIX 5L V5.3 1 |
Other Benchmark Information |
---|
The switch ports and all network adapters are 1Gb/sec. Requests were sent to the AppServers using DNS round robin, with the database node acting as the DNS server. This submission used the xerces implementation (version - XML4J 4.3) provided with WebSphere Application Server V6.1 in the IBM 1.5.0 JDK. |
General Notes |
---|
The only errors in the driver log files were those that are normally generated by this benchmark. The IBM DB2 Universal JDBC Drivers is a type 4 driver. 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 pages 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 a more detailed description of the general principles of the write-ahead-logging protocol, see the IBM research paper, ARIES: A Transaction Recovery Method Supporting Fine Granularity Locking and Partial Rollbacks Using Write-Ahead Logging," by C. Mohan, Database Technology Institute, IBM Almaden Research Center. (http:// portal.acm.org/citation.cfm ?id=128770&coll=portal&dl=ACM&CFID=10343790&CFTOKEN=42047146) 1-phase transactions were used to coordinate the interaction between the database server and JMS servers. |
For questions about this result, please contact the submitter: IBM Corporation For other inquiries, please contact webmaster@spec.org
Copyright © 2004 Standard Performance Evaluation Corporation
First published at SPEC.org on 12-Sep-2007