SPECjEnterprise®2010 Result Copyright © 2009-2014 Standard Performance Evaluation Corporation |
WebSphere Application Server V8.5.5.2 and DB2 10.5 on IBM Power S824 |
|
Submitter: IBM Corporation |
SPEC license # 11 | Test date: Mar-2014 |
SUT Configuration | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
Benchmark Settings | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
WebSphere Application Server V8.5.5.2 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
IBM J9 VM (build 2.7, JRE 1.7.1 IBM J9 AIX ppc-32) | ||||||
---|---|---|---|---|---|---|
|
IBM J9 VM (build 2.6, JRE 1.6.0 IBM J9 Linux x86-32) | ||||||
---|---|---|---|---|---|---|
|
IBM DB2 Universal JDBC Drivers (3.65.109) | ||||||
---|---|---|---|---|---|---|
|
DB2 10.5 FP3 | ||||||
---|---|---|---|---|---|---|
|
IBM InfoSphere Optim pureQuery Runtime v3.1.1 | ||||||
---|---|---|---|---|---|---|
|
JEE Application Server | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
Emulator Software Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Database Software Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Driver 1 Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Driver 2 Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
JEE AppServer HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||
|
Emulator HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||
|
Master & Load Driver 1 HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Driver 2 HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Benchmark Modifications |
---|
Schema Modifications:
Scripts to create the database are included in the FDA. All tables except the following are range partitioned: S_SUPPLIER, S_RUN_CONFIG, U_SEQUENCES, U_DATASEGMENT, U_LOADER, U_LOAD_MESSAGE, U_LOAD_SECTION New indexes are added to the following tables: M_INVENTORY, M_PARTS, S_SUPP_COMPONENT |
Load Program Modifications:
No modifications to the load programs were made. |
Benchmark Configuration Information |
---|
Isolation Requirement Info:
The benchmark meets the isolation level requirements by version column checking on entities against the database. The ItemEnt bean was cached for 20 minute intervals using the WebSphere JPA Object Cache mechanism. |
Durability Requirement Info:
To ensure database durability, the database and the database logs were each maintained on 8 mirrored internal 400GB SSD drives |
Storage Requirement Info:
Over the course of a 85 minute run at an injection rate of 14173, the database storage for database system increased by 61 GB. Given a linear scale, a 24 hour run at the same injection rate would increase storage for database system by 1039 GB. The database was configured with 1400 GB of mirrored storage. |
Bill of Materials |
---|
Supplier Description Product # Qty -------- ------------------------------------------- ---------------- --- Application Server: IBM IBM Power S824 Model 42A 8286-42A 1 IBM AC POWER SUPPLY, 100-127V/200-240V, 900 WATT EB2L 4 IBM LANGUAGE SPECIFY ENGLISH 9300 1 IBM PRIMARY OPERATING SYSTEM INDICATOR - AIX 2146 1 IBM AIX PARTITION SPECIFY (ONE PER PARTITION) 265 1 IBM IBM BEZEL + MISC HDWR & LOW FUNCTION BP FILLER, - 42A RACK-MOUNT DRAWER EJTC 1 IBM PWR CBL, DRWR TO IBM PDU, MFG SEL LENGTH, - 200-240V/10A, IEC320/C13, IEC320/C14 6577 4 IBM 8GB DDR3 1600Mhz MEMORY ACTIVATION EMA5 64 IBM 4U SAS RAID 0,10 PKG + CNTRLR CD + - 2X MINI SAS HD CBL + BP(12X SFF + SAS SLIM DVD) - (SOLSTICE 4U, MIAOKOU) EJ0N 1 IBM 300GB 15K RPM SAS HDD, SFF IN GEN3 CARRIER ESDB 2 IBM SATA DVDRAM WITH WRITE CACHE, SLIM-LINE 5771 1 IBM DUAL PORT E`NET (2X SFP+(SR) 10Gb), PCIE2-8X/LPC 5287 2 IBM PCIe2 4-port(10Gb FCoE & 1GbE) SR&RJ45 EN08 1 IBM 1Gb E`NET(UTP) 4-PORT ADPTR, PCIE-x4/SHORT, - LOW-PROFILE CAPABLE 5899 6 IBM INDICATOR FOR RACK #01 4651 1 IBM 0/12W 3.591GHz P8 DCM 220W + 4U HEAT SINK + TIM PAD EPXH 2 IBM ($0 #EPYH) 1W PROC ENTITLEMENT FOR #EPXH EPZH 12 IBM 32GB CDIMM (1.35V), 1600MHZ, 4GBIT DDR3 DRAM (2RX8), - SHORT W/EXTENDER EM8C 16 IBM 1W PROC ENTITLEMENT FOR #EPXH EPYH 12 ... Database Server: IBM IBM Power S824 Model 42A 8286-42A 1 IBM AC POWER SUPPLY, 100-127V/200-240V, 900 WATT EB2L 2 IBM LANGUAGE SPECIFY ENGLISH 9300 1 IBM PRIMARY OPERATING SYSTEM INDICATOR - AIX 2146 1 IBM AIX PARTITION SPECIFY (ONE PER PARTITION) 265 1 IBM IBM BEZEL + MISC HDWR & LOW FUNCTION BP FILLER, - 42A RACK-MOUNT DRAWER EJTC 1 IBM PWR CBL, DRWR TO IBM PDU, MFG SEL LENGTH, - 200-240V/10A, IEC320/C13, IEC320/C14 6577 4 IBM 64GB CDIMM (1.35V), 1600MHZ, 4GBIT DDR3 DRAM (2RX4), - DDP SHORT W/EXTENDER EM8D 16 IBM 8GB DDR3 1600Mhz MEMORY ACTIVATION EMA5 128 IBM 4U SAS RAID 0,5,6,10 + 2X CNTR +2X MINI SAS CBL - + BP(18X SFF + 8X SSD + SAS SLIM DVD +2X EXT PT) - (4U GX ... EJ0P 1 IBM 300GB 15K RPM SAS HDD, SFF IN GEN3 CARRIER ESDB 2 IBM SATA DVDRAM WITH WRITE CACHE, SLIM-LINE 5771 1 IBM DUAL PORT E`NET (2X SFP+(SR) 10Gb), PCIE2-8X/LPC 5287 3 IBM 1Gb E`NET(UTP) 4-PORT ADPTR, PCIE-x4 5899 1 IBM INDICATOR, FC 5887/EL1S FULL DRAWER, MODE 1, - ONE CUBIC-J (ESA1/ESA2/EL2K), ONE 6G YO CABLES EJP1 1 IBM INDICATOR FOR RACK #01 4651 1 IBM 0/12W 3.591GHz P8 DCM 220W + 4U HEAT SINK + TIM PAD EPXH 2 IBM ($0 #EPYH) 1W PROC ENTITLEMENT FOR #EPXH EPZH 12 IBM 1W PROC ENTITLEMENT FOR #EPXH EPYH 12 IBM 387GB SAS SFF SSD S/S DRIVE IN GEN 3 CARRIER ES0L 16 ... Software: IBM DB2 Enterprise Server Edition v10.5.0.3 D55IULL 24* - Lic+SW Maint 12 Months IBM DB2 Enterprise Server Edition v10.5.0.3 E020CLL 48 - SW Maint Rewl 1 Anniv IBM WebSphere Application Server V8.5.5.2 D55W8LL 24* - Lic+SW Maint 12 Months IBM WebSphere Application Server V8.5.5.2 E025QLL 48 - SW Maint Rewl 1 Anniv IBM IBM Optim Purequery Runtime for LUW 3.1.1 D61YKLL 24* - Lic+SW Maint 12 Months IBM IBM Optim Purequery Runtime for LUW 3.1.1 E048YLL 48 - SW Maint Rewl 1 Anniv ... * Note: Pricing is based on Processor Value Units (PVU). Each core is 70 PVU. |
Other Benchmark Information |
---|
DNS round robin load balancing was used and hosted on the database machine. Network connectivity between the application server system and the switch outside of the SUT was 1Gps. All other connections were 10Gps. |
General Notes |
---|
All exceptions in driver logs are from Optimistic Concurrency Checking. These exceptions are expected in the 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 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 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 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. 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) |
For questions about this result, please contact the submitter: IBM Corporation For other inquiries, please contact webmaster@spec.org
Copyright © 2009-2014 Standard Performance Evaluation Corporation
First published at SPEC.org on 22-Apr-2014