SPECjEnterprise®2010 Result Copyright © 2009-2010 Standard Performance Evaluation Corporation |
WebSphere Application Server V7 on IBM System x3650 and DB2 9.7 on IBM System x3850 |
|
Submitter: IBM Corporation |
SPEC license # 11 | Test date: Feb-2010 |
SUT Configuration | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
Benchmark Settings | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
WebSphere Application Server V7 (Level 7.0.0.9) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux x86-32) | ||||||
---|---|---|---|---|---|---|
|
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64) | ||||||
---|---|---|---|---|---|---|
|
IBM DB2 Universal JDBC Drivers (3.58.82) | ||||||
---|---|---|---|---|---|---|
|
DB2 9.7 FP1 | ||||||
---|---|---|---|---|---|---|
|
JEE Application Server | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||
|
Emulator Software Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Database Software Config | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Driver Config | ||||||
---|---|---|---|---|---|---|
|
||||||
|
JEE AppServer HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||
|
Load Driver HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
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 OpenJPA Data cache mechanism. |
Durability Requirement Info:
To ensure database durability, RAID10 was used for the database logs maintained on the external storage. A total of 16 x 33GB disks were used for the log. |
Storage Requirement Info:
Over the course of a 85 minute run at an injection rate of 755, the database storage for database system increased by 7.42 GB. Given a linear scale, a 24 hour run at the same injection rate would increase storage for database system by 125.70 GB. One RAID10 disk arrays were used to create the filesystem space for the database. The array contained 16 x 33GB disks providing 267 Gb GB of storage. |
Bill of Materials |
---|
Supplier Description Product # Qty -------- ------------------------------------------- ---------------- --- IBM IBM System x3850 M2 7233AC1 1 - 2xSix Core Intel Xeon Processor X7460 - (2.67GHz 16MB L3 130w) - 64GB RAM (32x2GB DIMMS), 2x146GB 10k SAS HDD IBM DS4800 Disk System Model 82 (4 GB Cache) 1815-82A 1 IBM DS4000 EXP810 Expansion Unit Model 81 1812-81A 2 IBM 4 Gbps FC, 36.4 GB/15K E-DDM 5433 32 IBM 3 Year Onsite Repair 24x7 4 Hour Response 6756001 1 IBM SUSE Linux Enterprise Server w/ 3yr support 5639S1X 1 ... IBM IBM System x3650 M2 325254-B21 7947AC1 1 - 2xIntel Xeon Processor X5570 4C - (2.93GHz 8MB L3 Cache 1333MHz 95w) - 24GB RAM (6x4GB DIMMS), 1x146GB 10k SAS HDD IBM 3 Year Onsite Repair 24x7 4 Hour Response 6756025 IBM SUSE Linux Enterprise Server w/ 3yr support 5639S1X 1 ... CDW NETGEAR GS116 16-port 10/100/1000Mbps 638864 1 - Gigabit Switch CDW NETGEAR 3 Year ProSupport Maintenance PMB0331NA 1 - Contract - OnCall 24x7 - Category 1 IBM DB2 Enterprise Server Edition 9.7 D597RLL 12* - Lic+SW Maint 12 Months IBM DB2 Enterprise Server Edition 9.7 E00BILL 24 - SW Maint Rewl 1 Anniv IBM WebSphere Application Server V7 D55W8LL 8** - Lic+SW Maint 12 Months IBM WebSphere Application Server V7 E1CBBLL 16 - SW Maint Rewl 1 Anniv ... * Note: Pricing for DB2 is based on Value Units (VU). Each Intel core is 50 VU. ** Note: Pricing for WebSphere is based on Value Units (VU). Each Intel core is 70 VU. |
Other Benchmark Information |
---|
DNS round robin load balancing was used and hosted on the database machine All network connections were 1Gbps |
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-2010 Standard Performance Evaluation Corporation
First published at SPEC.org on 25-Feb-2010