![]() |
SPECjAppServer®2004 Result Copyright © 2004 Standard Performance Evaluation Corporation |
WebSphere 6.0 Application Server on IBM eServer OpenPower 720 Cluster |
|
Submitter: IBM Corporation |
SPEC license # 11 | Test date: Dec-2004 |
SUT Configuration | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
Benchmark Settings | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
WebSphere 6.0 Application Server Network Deployment | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) | ||||||
---|---|---|---|---|---|---|
|
IBM DB2 Universal JDBC Drivers | ||||||
---|---|---|---|---|---|---|
|
IBM DB2 V8.2 | ||||||
---|---|---|---|---|---|---|
|
IBM Load balancer, Edge Component of WebSphere V6.0 | ||||||
---|---|---|---|---|---|---|
|
WebSphere V6.0 Deployment Manager | ||||||
---|---|---|---|---|---|---|
|
J2EE Application Servers | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
Emulator SW Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Database SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver SW Config Primary | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver SW Config Satellites #1 | ||||||
---|---|---|---|---|---|---|
|
||||||
|
IBM Load Balancer 6.0 | ||||||
---|---|---|---|---|---|---|
|
||||||
|
J2EE Application Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Balancer and WebSphere Deployment Manager Hardware (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Emulator (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Drivers (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 (Access Intent's of wsOptimisticUpdate or wsOptimisticRead) which is Cursor Stability (CS) for DB2. The remaining beans were accessed using REPEATABLE_READ (Access Intent's of wsPessimisticUpdate, wsPessimisticRead or wsPessimisticWeakestLockAtLoad) which translates to DB2 isolation level of Read Stability (RS). The ItemEnt bean was cached for 20 minute intervals using the WebSphere Read Only Bean Mechanism. Only the data inside the bean was cached. |
Durability Requirement Info:
To ensure database durability, RAID 5 was used for the database logs maintained on the DS4300 Storage Expansion Units. |
Storage Requirement Info:
Over the course of a 89 minute run at an injection rate of 800, the database storage for database system increased by 914 MB; Given a linear scale, a 24 hour run at the same injection rate would increase storage for database system by 14784 MB. The DS4300 disk array each contain seven 18 GB drives. The DS4300 controller utilized these drives as a RAID 0 array, yielding 126 GB for available storage. |
Argument Passing Semantics:
WebSphere Application Server V6.0 uses pass-by-value semantics by default. |
Bill of Materials |
---|
IBM eServer OpenPower 720 WebSphere 6.0 Cluster with DB2 v8.2 Database Server Supplier IBM eServer OpenPower 720 WebSphere V6 Hardware (for four systems) Unit Qty Description Part Number IBM 4 9124 Model 720 9124-720 IBM 16 1024MB (4x256MB) DIMMs, 208-pin, 266 MHz DDR SDRAM 1937 IBM 4 IDE Slimline DVD-ROM Drive 2640 IBM 8 36.4 GB 10,000 RPM Ultra320 SCSI Disk Drive 3273 IBM 8 2-way 1.65 GHz POWER5 Processor Card, 36MB L3 Cache 5262 IBM 4 Power Cable -- Drawer to IBM PDU, 250v/10A 6458 IBM 4 4-Disk Slot Exp - Base Ctlr 6592 IBM 4 IBM Rack-mount Drawer Rail Kit 7162 IBM 8 CPU Power Regulator 7876 IBM 4 Media Backplane Card 7877 IBM 4 1475W AC Power Supply 7889 IBM 4 720 Rack Mount 7914 IBM 4 Language Group: US English 9300 IBM 4 3 year support, 24x7x4 38R3592 Supplier IBM eServer OpenPower 720 Database Hardware (for one system) Unit Qty Description Part Number IBM 1 9124 Model 720 9124-720 IBM 4 4096MB (4x1024MB) DIMMs, 208-pin, 266 MHz DDR SDRAM 1940 IBM 1 IDE Slimline DVD-ROM Drive 2640 IBM 2 36.4 GB 10,000 RPM Ultra320 SCSI Disk Drive 3273 IBM 2 2-way 1.65 GHz POWER5 Processor Card, 36MB L3 5262 IBM 1 2 Gigabit Fibre Channel PCI-X Adapter 5716 IBM 1 Power Cable -- Drawer to IBM PDU, 250v/10A 6458 IBM 1 4-Disk Slot Exp - Base Ctlr 6592 IBM 1 IBM Rack-mount Drawer Rail Kit 7162 IBM 2 CPU Power Regulator 7876 IBM 1 Media Backplane Card 7877 IBM 1 1475W AC Power Supply 7889 IBM 1 720 Rack Mount 7914 IBM 1 Language Group: US English 9300 IBM 1 3 year suport, 24x7x4 38R3592 Supplier IBM Storage Hardware (for database system) Unit Qty Description Part Number IBM 1 DS4300 Midrange Disk (6LU) 1720-6LU IBM 1 Short Wave SFP GBIC (LC) 2210 IBM 14 2Gb FC, 18.2GB/15K Drive Module 5211 IBM 1 DS4300 Linux for Power Host Kit 7714 IBM 1 Field Integrate DS4300 9202 IBM 1 3 year support, 24x7x4 96P2368 Supplier IBM eServer OpenPower 720 Load Balancer and Deployment Manager Hardware (for one system) Unit Qty Description Part Number IBM 1 9124 Model 720 9124-720 IBM 2 1024MB (4x256MB) DIMMs, 208-pin, 266 MHz DDR SDRAM 1937 IBM 1 IDE Slimline DVD-ROM Drive 2640 IBM 2 36.4 GB 10,000 RPM Ultra320 SCSI Disk Drive 3273 IBM 2 2-way 1.5 GHz POWER5 Processor Card, L3 Cache 1961 IBM 1 Power Cable -- Drawer to IBM PDU, 250v/10A 6458 IBM 1 4-Disk Slot Exp - Base Ctlr 6592 IBM 1 IBM Rack-mount Drawer Rail Kit 7162 IBM 2 CPU Power Regulator 7876 IBM 1 Media Backplane Card 7877 IBM 1 1475W AC Power Supply 7889 IBM 1 720 Rack Mount 7914 IBM 1 Language Group: US English 9300 IBM 1 3 year suport, 24x7x4 38R3592 Supplier Miscellaneous Hardware Unit Qty Description Part Number IBM 1 HMC 1:7310-C03 Desktop Hardw.Mgmt.Console 7310-C03 IBM 1 Quiet Touch Keyboard - USB, Business Black, 8800 IBM 1 Mouse - Business Black with Keyboard Attachment Cable 8841 IBM 1 IBM ThinkVision L170 Monitor 3631 IBM 1 HMC Support, 3 year, 24x7x4 0569 IBM 1 NetBAY42 ER Enterprise Rack 930842S IBM 1 NetBay - 3yr Warranty Service Upgrade (24x7x4) 41L2762 CDW 1 Cisco 3750-24-TS 497268 CDW 3 Cisco Support 1 year, 24x7x4 150984 Supplier Passport Advantage Software Unit Qty Description Part Number IBM 8 DB2 UDB WORKGROUP SERVER UNLIMITED EDITION PROCESSOR LIC+SW MAINT 12 MO D51NDLL IBM 16 DB2 UDB WORKGROUP SERVER UNLIMITED EDITION PROCESSOR SW MAINT RNWL 1 ANNIV E00IHLL IBM 1 WAS NETWORK DEPLOYMENT V6.0.0 Multilingual MEDIA PK BA0DMML IBM 22 WAS Network Deployment Per Processor License & SW Maintenance 12 Months D5ALTLL IBM 44 WAS Network Deployment Per Processor SW Maintenance Annual Renewal E1ALVLL IBM 1 EDGE SERVER - LOAD BALANCING, CACHING,CENTRALIZED SECURITY included in D5ALTLL IBM 1 EDGE SERVER - SUPPORT included in E1ALVLL Supplier Operating System Software Unit Qty Description Part Number SuSE 1 SUSE LINUX ENTERPRISE SERVER 9 FOR POWER 5639-SLP SuSE 6 PREMIUM SUPPORT FOR SLES9 POWER FOR 3 YEARS SUSE QUOTE SuSE 6 MAINTENANCE PROGRAM FOR SLES9 X86 FOR 3 YEARS SUSE QUOTE |
Other Benchmark Information |
---|
The switch ports and all network adapters are 1Gb/sec. Two types of load balancing were utilized: WebSphere's workload management performed load balancing for RMI/IIOP requests. IBM Load Balancer balanced HTTP connections across the WebSphere nodes. This submission used the xerces implementation (version - XML4J 4.3) provided with WebSphere Application Server V6.0 in the IBM 1.4.2 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 05-Jan-2005