Copyright © 2009-2013 Standard Performance Evaluation Corporation
|
|
SPECjEnterprise®2010 Result Copyright © 2009-2013 Standard Performance Evaluation Corporation |
| WebSphere Application Server V8.5 and DB2 10.1 on IBM PowerLinux 7R2 |
|
| Submitter: IBM Corporation |
SPEC license # 11 | Test date: Feb-2013 |
| SUT Configuration | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
| Benchmark Settings | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Detailed Results | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||
|
| WebSphere Application Server V8.5 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| IBM J9 VM (build 2.6, JRE 1.7.0 IBM J9 Linux ppc-32) | ||||||
|---|---|---|---|---|---|---|
|
| IBM J9 VM (build 2.6, JRE 1.7.0 IBM J9 Linux x86-64) | ||||||
|---|---|---|---|---|---|---|
|
| IBM DB2 Universal JDBC Drivers (3.63.123) | ||||||
|---|---|---|---|---|---|---|
|
| DB2 10.1 FP2 | ||||||
|---|---|---|---|---|---|---|
|
| IBM InfoSphere Optim pureQuery Runtime v3.1.1 | ||||||
|---|---|---|---|---|---|---|
|
| 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:
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, RAID10 was used for the
database and database logs maintained on the external storage.
A total of 4 x 600GB disks were used for the log.
|
Storage Requirement Info:
Over the course of a 95 minute run at an injection rate of
7550, the database storage for database system increased by 10.25 GB.
Given a linear scale, a 24 hour run at the same
injection rate would increase storage for database system by 155.37 GB.
One RAID10 disk array was used to create the
filesystem space for the database. The array contained
20 x 600GB disks providing over 4 TB of storage.
|
| Bill of Materials |
|---|
Supplier Description Product # Qty -------- ------------------------------------------- ---------------- --- IBM IBM PowerLinux 7R2 8246-L2D 1 IBM Linux Partition Specify 0266 1 IBM Primary OS - Linux 2147 1 IBM Software Preload Required 5000 1 IBM PCIe2 LP 4-Port 10GbE&1GbE SFP+ Copper&RJ45 5279 2 IBM System AC Power Supply, 1925 W 5532 2 IBM SATA Slimline DVD-RAM Drive 5762 1 IBM Power Cord 2.7M (9-foot), Drawer to IBM 6671 2 - PDU, 250V/10A IBM Linux Software Preinstall 8143 1 IBM New Red Hat License Core Counter 9442 16 IBM RHEL for POWER 5639-RHP 3 IBM Per Svr up to 2 Skts IPL w/max 1 LPARs 0385 3 - w/1yr STD Sub IBM 600GB 10K RPM SFF SAS Disk Drive - PowerLinux EL0P 2 IBM Memory Riser Card - PowerLinux (zero priced) EL0A 1 IBM Memory Riser Card - PowerLinux EL0K 3 IBM Storage Backplane -- 6 SFF Drives/SATA DVD/RAID EL0V 1 IBM 16GB (2x8GB) Memory DIMMs - PowerLinux EL2Q 8 IBM PowerLinux Base package -- 16-core 4.2 GHz ELBD 1 IBM 8-core 4.2 GHz POWER7+ Processor Module EPLK 2 IBM Processor Activation for #EPLK (Zero-priced) EPLN 16 IBM Warranty Service Upgrade 6942-25B 3 IBM WSU Same Day 24x7x4 Response 4524 3 ... IBM IBM PowerLinux 7R2 8246-L2D 1 IBM Linux Partition Specify 0266 1 IBM Primary OS - Linux 2147 1 IBM System Serial Port Converter Cable 3930 1 IBM Software Preload Required 5000 1 IBM PCIe LP 2-Port 1GbE TX Adapter 5281 3 IBM System AC Power Supply, 1925 W 5532 2 IBM SATA Slimline DVD-RAM Drive 5762 1 IBM Power Cord 2.7M (9-foot), Drawer to IBM 6671 2 - PDU, 250V/10A IBM Linux Software Preinstall 8143 1 IBM Language Group Specify - US English 9300 1 IBM New Red Hat License Core Counter 9442 16 IBM RHEL for POWER 5639-RHP 3 IBM Per Svr up to 2 Skts IPL w/max 1 LPARs 0385 3 - w/1yr STD Sub IBM 600GB 10K RPM SFF SAS Disk Drive - PowerLinux EL0P 2 IBM Memory Riser Card - PowerLinux 5265 3 IBM Storage Backplane -- 6 SFF Drives/SATA DVD/RAID EL0V 1 IBM 32GB (2x16GB) Memory DIMMs - PowerLinux EL2T 8 IBM PowerLinux Base package -- 16-core 4.2 GHz ELBD 1 IBM 8-core 4.2 GHz POWER7+ Processor Module EPLK 2 IBM Processor Activation for #EPL5 (Zero-priced) EPLN 16 IBM PCIe LP 4Gb 2-Port Fibre Channel Adapter EL09 1 IBM Warranty Service Upgrade 6942-25B 3 IBM WSU Same Day 24x7x4 Response 4524 3 ... IBM IBM Storwize V7000 Disk Control Enclosure 2076-124 1 IBM Storage Engine Preload 0010 1 IBM 600GB 6Gb SAS 10K 2.5-inch SFF HDD 3546 24 IBM 1 m Fiber Optic Cable LC-LC 5301 2 IBM Cache 8 GB 6008 2 IBM Power Cord - PDU connection 9730 1 IBM AC Power Supply 9801 2 IBM 3 Year Onsite Repair 24x7 4 Hour Response ... IBM DB2 Enterprise Server Edition 10.1 D55IULL 16* - Lic+SW Maint 12 Months IBM DB2 Enterprise Server Edition 10.1 E020CLL 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 E025QLL 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 core is 70 PVU. |
| Other Benchmark Information |
|---|
DNS round robin load balancing was used and hosted on the database machine All network connectivity to the database system was 1Gbps 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-2013 Standard Performance Evaluation Corporation
First published at SPEC.org on 22-Feb-2013
