Copyright © 2009-2012 Standard Performance Evaluation Corporation
|
|
SPECjEnterprise®2010 Result Copyright © 2009-2012 Standard Performance Evaluation Corporation |
| WebSphere Application Server V8.5 on IBM System HS22 and DB2 9.7 on IBM System x3850 X5 |
|
| Submitter: IBM Corporation |
SPEC license # 11 | Test date: Apr-2012 |
| SUT Configuration | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
| Benchmark Settings | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Detailed Results | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
| WebSphere Application Server V8.5 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| IBM J9 VM (build 2.6, JRE 1.7.0 IBM J9 Linux x86-32) | ||||||
|---|---|---|---|---|---|---|
|
| IBM J9 VM (build 2.6, JRE 1.6.0 IBM J9 Linux x86-32) | ||||||
|---|---|---|---|---|---|---|
|
| IBM DB2 Universal JDBC Drivers (3.62.56) | ||||||
|---|---|---|---|---|---|---|
|
| DB2 9.7 FP4 | ||||||
|---|---|---|---|---|---|---|
|
| JEE Application Server | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||
|
| Emulator Software Config | ||||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
|
| Database Software Config | ||||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
|
| Driver Config | ||||||
|---|---|---|---|---|---|---|
|
||||||
|
| JEE AppServer HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||
|
| Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||
|
| Load Driver & Emulator HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
| Benchmark Modifications |
|---|
Schema Modifications:
No modifications to the schema where made. |
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 90 minute run at an injection rate of
3950, the database storage for database system increased by
6 GB. Given a linear scale, a 24 hour run at the same
injection rate would increase storage for database system
by 102 GB. One RAID10 disk array was used to create the
filesystem space for the database. The array contained
24 x 146GB disks providing 1752 GB of storage.
|
| Bill of Materials |
|---|
Supplier Description Product # Qty -------- ------------------------------------------- ---------------- --- IBM IBM System x HS22 7870C8U 1 IBM Intel Xeon Processor X5690 6C - (3.47GHz 12MB L3 Cache 1333MHz 130W) A18G 1 IBM Addl Intel Xeon Processor X5690 6C 3.46GHz A16C 1 IBM 4GB (1x4GB, 2Rx8, 1.35V) PC3L-10600 DDR3 1333MHz A0WZ 12 IBM 146 GB 10K SAS 2.5 SFF Slim-HS HDD 1049 2 IBM 10Gb 4-Port Ethernet Card (CFFh) for IBM BladeCenter 0098 1 IBM 3 Year Onsite Repair 24x7 4 Hour Response 675669D IBM SUSE Linux Enterprise Server w/ 3yr support 5639S1X 1 IBM IBM BladeCenter H 88524TU 1 IBM 10Gb Ethernet Pass-Thru Module for IBM BladeCenter 46M6181 4 IBM 10GbE Fiber SFP+ Transceiver 44W4408 4 IBM 3 Year Onsite Repair 24x7 4 Hour Response 40Y5981 1 ... IBM IBM System x3850 X5 7143B7U 1 - 2xIntel Xeon Processor E7-4870 10C - (2.40GHz 30MB L3 Cache 130W) IBM Addl Intel Xeon Processor E7-4870 10C 2.40GHz 69Y1893 2 IBM X3850 X5 Memory Expansion Card 69Y1888 4 IBM x3850 QPI Wrap Card 49Y4379 2 IBM 4GB (1x4GB, 2Rx8, 1.35V) PC3L-10600 DDR3 1333MHz 49Y1407 64 IBM 146GB 15K SAS 2.5 SFF HDD 42D0677 2 IBM 8Gb FC Dual-port HBA for IBM System x 42D0510 2 IBM 10 GbE Adapter for IBM System x 81Y9990 2 IBM 10GbE Fiber SFP+ Transceiver 44W4408 3 IBM 3 Year Onsite Repair 24x7 4 Hour Response 84Y2233 IBM SUSE Linux Enterprise Server w/ 3yr support 48153RU 1 IBM IBM System Storage DS3524 Express 1746-C4A 3 IBM 146GB 15,000 rpm 6Gb SAS 2.5; HDD 5205 72 IBM 3 Year Onsite Repair 24x7 4 Hour Response 67567DT ... IBM DB2 Enterprise Server Edition 9.7 D55IULL 20* - Lic+SW Maint 12 Months IBM DB2 Enterprise Server Edition 9.7 E020CLL 40 - SW Maint Rewl 1 Anniv IBM WebSphere Application Server V8.5 D55W8LL 12** - Lic+SW Maint 12 Months IBM WebSphere Application Server V8.5 E025QLL 24 - SW Maint Rewl 1 Anniv ... * Note: Pricing for DB2 is based on Processor Value Units (PVU). Each Intel core is 100 PVU. ** Note: Pricing for WebSphere is based on Processor Value Units (PVU). Each Intel core is 70 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 26-Apr-2012
