SPECjAppServer®2004 Result Copyright © 2004 Standard Performance Evaluation Corporation |
WebSphere 6.1 Application Server on xSeries Blade Center |
|
Submitter: IBM Corporation |
SPEC license # 11 | Test date: Jul-2006 |
SUT Configuration | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
Benchmark Settings | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
||||||||||||||||||||||||||
|
WebSphere Application Server V6.1.0.1 64-bit | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
WebSphere Application Server V6.1.0.1 32-bit | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Java(TM) 2 Runtime Environment, Standard Edition 1.5.0 (build pxa64dev-20060511 (SR2)) | ||||||
---|---|---|---|---|---|---|
|
Java(TM) 2 Runtime Environment, Standard Edition 1.5.0 (build pxi32dev-20060511 (SR2)) | ||||||
---|---|---|---|---|---|---|
|
Java(TM) 2 Runtime Environment, Standard Edition 1.5.0 (build pwi32dev-20060511 (SR2)) | ||||||
---|---|---|---|---|---|---|
|
IBM DB2 Driver for JDBC and SQLJ | ||||||
---|---|---|---|---|---|---|
|
IBM DB2 9.1 | ||||||
---|---|---|---|---|---|---|
|
J2EE Application Servers | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
Emulator SW Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Database SW Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver SW Config Primary and Satellites | ||||||
---|---|---|---|---|---|---|
|
||||||
|
J2EE Application Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
BIND Load Balancer Hardware (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Emulator (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Drivers Primary and Satellites #1-#12 (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, RAID 10 (mirrored stripe) was used for the database logs maintained on the external storage. The array contains fourteen 36 GB drives for this purpose. |
Storage Requirement Info:
Over the course of a 75 minute run at an injection rate of 2660, the database storage for database system increased by 2531 MB. Given a linear scale, a 24 hour run at the same injection rate would increase storage for database system by 48595.2 MB. The disk array contains fourteen 36 GB drives. The DS4300 controller utilized these drives as a RAID 10 array, yielding 252 GB for available storage. |
Argument Passing Semantics:
WebSphere Application Server V6.1.0.1 uses pass-by-value semantics by default. |
Bill of Materials |
---|
IBM xSeries BladeCenter WebSphere 6.1 64-bit with IBM DB2 9.1 Database Server Supplier IBM xSeries BladeCenter WebSphere 6.1 64-bit Hardware (for twenty systems) Unit Qty Description Model Number IBM 2 IBM BladeCenter Chassis 86773XU 2 Cisco Systems Intelligent Gigabit Ethernet Switch 26K6547 Module for the IBM eServer BladeCenter 2 Nortel Networks Layer 2/3 Copper GbE Switch Module 32R1860 for IBM eServer BladeCenter IBM 20 BladeCenter HS20 2-WAY 3.6GHz 2MB L2 Cache Intel 884345U Xeon Processors with 2x2GB (2x1GB) PC2-3200 ECC DDR SDRAM RDIMM Kit, and 1x73GB Non Hot-Swap 2.5 10K RPM Ultra320 SCSI HDD IBM 20 3 year support, 24x7x4 Supplier IBM eServer p5 570 Database Hardware (for one system) Unit Qty Description Part Number IBM 1 9117 Model 570 9117-570 IBM 4 36.4 GB 15,000 RPM Ultra320 SCSI Disk Drive Assembly 3277 IBM 16 8192MB (4x2048MB) DIMMs, 208-pin, 8NS Stacked DDR 4454 IBM 2 2 Gigabit Fibre Channel PCI-X Adapter 5716 IBM 8 Processor, 0/2 Way 1.9 GHz with DDR1 memory 7832 IBM 1 3 year support, 24x7x4 Supplier IBM Storage Hardware (for database system) Unit Qty Description Part Number IBM 1 DS4300 Midrange Disk (6OU) 1722-6OU IBM 1 TotalStorage DS4000 EXP710Storage Expansion Unit 1740-710 IBM 28 2Gb FC, 36.4GB/15K Drive Module 1722-5212 IBM 1 DS4300 1st EXP700/710 Attach 1722-7361 IBM 1 DS4300 AIX Host Kit 1722-7711 IBM 1 3 year support, 24x7x4 Supplier IBM xSeries x336 Load Balancer Hardware (for one system) Unit Qty Description Part Number IBM 1 xSeries x336 1-way 2.8Ghz 2MB L2 Cache Intel 883706U Xeon Processors with (2) IBM 512MB PC2-3200 DDR2 SDRAM, and 1x80GB SATA 7200 HDD, 2xNetXtreme 1000 T + Dual Port Server Adapter IBM 1 3 year suport, 24x7x4 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 C117 17" CRT Monitor 3631 IBM 1 HMC Support, 3 year, 24x7x4 0569 CDW 1 3Com 10/100/1000 Switch - switch - 8 ports 622795 CDW 3 3Com Support 1 year, 24x7x4 820685 Supplier Passport Advantage Software Unit Qty Description Part Number IBM 16 DB2 UDB ENTERPRISE SERVER EDITION PROCESSOR LIC+SW MAINT 12 MO D51NDLL IBM 16 DB2 UDB ENTERPRISE SERVER EDITION PROCESSOR SW MAINT RNWL 1 ANNIV E00BILL IBM 40 IBM WebSphere Application Server Processor License+SW Maintenance 12 Months D5CB9LL IBM 80 IBM WebSphere Application Server SW Maintenance 12 Months E1CBBLL Supplier Operating System Software Unit Qty Description Part Number Novell 2 SUSE LINUX ENTERPRISE SERVER 9 for IBM BladeCenter w/1yr support Novell 1 SUSE LINUX ENTERPRISE SERVER 9 Novell 4 SUSE LINUX ENTERPRISE SERVER 9 for IBM BladeCenter Support Novell 2 SUSE LINUX ENTERPRISE SERVER 9 |
Other Benchmark Information |
---|
The switch ports and all network adapters are 1Gb/sec. Load balancing was performed using DNS round robin routing This submission used the xerces implementation (version - XML4J 4.3) provided with WebSphere Application Server V6.1.0.1 in the IBM 1.5.0 JDK (build pxa64dev-20060511 (SR2)). |
General Notes |
---|
The only errors in the driver log files were those that are normally generated by this benchmark. The IBM DB2 Driver for JDBC and SQLJ 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 02-Aug-2006