Copyright © 2009-2012 Standard Performance Evaluation Corporation
|
|
SPECjEnterprise®2010 Result Copyright © 2009-2012 Standard Performance Evaluation Corporation |
| WebSphere Application Server V8.5 on 16-core LPAR IBM Power 780 and DB2 10.1 on 16-core LPAR IBM Power 780 |
|
| Submitter: IBM Corporation |
SPEC license # 11 | Test date: Sep-2012 |
| SUT Configuration | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
| Benchmark Settings | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Detailed Results | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
| WebSphere Application Server V8.5 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| IBM J9 VM (build 2.6, JRE 1.7.0 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.63.123) | ||||||
|---|---|---|---|---|---|---|
|
| DB2 10.1 | ||||||
|---|---|---|---|---|---|---|
|
| IBM InfoSphere Optim pureQuery Runtime v3.1.1 | ||||||
|---|---|---|---|---|---|---|
|
| JEE Application Server | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||
|
| Emulator Software Config | ||||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
|
| Database Software Config | ||||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
|
| Driver Config | ||||||
|---|---|---|---|---|---|---|
|
||||||
|
| JEE AppServer & Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||||||
|
| Emulator HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||
|
| Load Driver 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 |
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, RAID10 was used for the
database logs maintained on the external storage.
A total of 48 x 146GB disks were used for the log.
|
Storage Requirement Info:
Over the course of a 88 minute run at an injection rate of
6845, the database storage for database system increased by
7 GB. Given a linear scale, a 24 hour run at the same
injection rate would increase storage for database system
by 115 GB. One RAID10 disk array was used to create the
filesystem space for the database. The array contained
16 x 400GB disks providing 2 TB of storage.
|
| Bill of Materials |
|---|
Supplier Description Product # Qty -------- ------------------------------------------- ---------------- --- IBM IBM Power 780 9179-MHB 1 - 8x4-core POWER7+ Processor - (4.424GHz 10MB L3 Cache per core) - 768GB RAM (16x8GB DIMMS, 16x16GB DIMMS), - 5x146.8GB 15k SAS HDD - 10 GB Ethernet SR PCI dual port 5721 6 - 10 GB Ethernet SR PCI 5769 2 - PCIE2 8GB 4port Fibre Channel 5729 3 - 3 Year Onsite Repair 24x7 4 Hour Response IBM AIX Standard Edition V7.1 TL2 per processor 5765-G98-0017 32 IBM AIX 3 year support per processor 5773-SM3-1259 32 ... IBM IBM System Storage DS3524 Express 1746-C4A 2 IBM 146GB 15,000 rpm 6Gb SAS 2.5; HDD 5205 48 IBM 3 Year Onsite Repair 24x7 4 Hour Response 67567DT IBM IBM Storwize V7000 Disk System 5639-VM1 1 IBM 400 GB 2.5INCH SSD (E MLC) 3543 16 IBM 3 Year Onsite Repair 24x7 4 Hour Response 67567DT ... IBM DB2 Enterprise Server Edition 10.1 D597RLL 16* - Lic+SW Maint 12 Months IBM DB2 Enterprise Server Edition 10.1 E00BILL 32 - SW Maint Rewl 1 Anniv IBM WebSphere Application Server V8.5 D55W8LL 16* - Lic+SW Maint 12 Months IBM WebSphere Application Server V8.5 E1CBBLL 32 - SW Maint Rewl 1 Anniv IBM IBM Optim Purequery Runtime for LUW 3.1.1 D61YKLL 16* - Lic+SW Maint 12 Months IBM IBM Optim Purequery Runtime for LUW 3.1.1 E048YLL 32 - SW Maint Rewl 1 Anniv ... * Note: Pricing is based on Processor Value Units (PVU). Each POWER7 core is 120 PVU. |
| Other Benchmark Information |
|---|
DNS round robin load balancing was used and hosted on the database machine All network connections were 10Gbps |
| 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 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) |
For questions about this result, please contact the submitter: IBM Corporation
For other inquiries, please contact
webmaster@spec.org
Copyright © 2009-2012 Standard Performance Evaluation Corporation
First published at SPEC.org on 03-Oct-2012
