![]() |
SPECjEnterprise®2018 Web Profile Result Copyright © 2009-2019 Standard Performance Evaluation Corporation |
WebSphere Liberty Core 19.0.0.3 on IBM Power S924 24-core POWER9 and DB2 11.1 on IBM Power S924 16-core POWER9 |
|
Submitter: IBM Corporation |
SPEC license # 11 | Test date: May-2019 |
SUT Configuration | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||
|
Benchmark Settings | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Detailed Results | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
WebSphere Liberty Core 19.0.0.3 | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
IBM SDK, Java Technology Edition, Version 8, Service Refresh 5, Fixpack 30 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
IBM DB2 Universal JDBC Drivers (4.25.13) | ||||||||
---|---|---|---|---|---|---|---|---|
|
DB2 11.1 Mod 4 Fix Pack 4 | ||||||||
---|---|---|---|---|---|---|---|---|
|
Insurance Java EE Configuration | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Insurance Provider Java EE Configuration | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Vehicle Java EE Configuration | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
Database SW Configuration | ||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
Driver Configuration | ||||||
---|---|---|---|---|---|---|
|
||||||
|
Java EE Web Profile Application Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Database Server HW (SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Load Driver HW (non-SUT hardware) | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||
|
Benchmark Modifications |
---|
Schema Modifications:
SQL files to load the database are included in the FDA. |
Load Program Modifications:
No modifications to the load programs were made. |
Benchmark Configuration Information |
---|
Isolation Requirement Info:
The READ_COMMITTED isolation level was used for all JPA entities. The vehicle service entity and queries were cached for 20 minute intervals. The Object Cache mechanism was set in the vehicle_orm.xml as follows: <cache> <expiry>1200000</expiry> </cache> The Query Cache mechanism was set in the vehicle_orm.xml for each of the queries with the property: <hint name="eclipselink.query-results-cache.expiry" value="1200000"/> The insurance provider service entities and queries were cached for 120 minute intervals. The Object Cache mechanism was set in the provider_orm.xml for each entity as follows: <cache> <expiry>7200000</expiry> </cache> The Query Cache mechanism was set in the provider_orm.xml for each of the queries with the property: <hint name="eclipselink.query-results-cache.expiry" value="7200000"/> |
Durability Requirement Info:
To ensure database durability, the database and the database logs were each maintained on one 1000 GB RAID5 SSD from IBM FlashSystem 900. The RAID controller is configured with a write-through policy. |
Storage Requirement Info:
Over the course of a 75 minute run at an injection rate of 34300, the database storage increased by 6.5 GB Given a linear scale, a 24 hour run at the same injection rate would increase storage by 124.8 GB. The database was configured with one 1000 GB RAID5 drive for logs and storage. |
Bill of Materials |
---|
----------------------------Application Server SUT---------------------------- Supplier Description Product # Qty -------- ------------------------------------------- ---------------- --- IBM IBM Power S924 Model 42A 9009-42A 1 IBM AC Power Supply - 1400W for Server EB2M 4 (200-240 VAC) IBM Rack Indicator, Rack #1 4651 1 IBM Power Cord 4.3m (14-ft), Drawer to IBM PDU 6458 4 (250V/10A) IBM Language Group Specify - US English 9300 1 IBM Primary OS - Linux 2147 1 IBM Linux Partition Specify 0266 1 IBM PowerVM Enterprise Edition 5228 24 IBM Expanded Function Storage Backplane EJ1D 1 18 SFF-3 Bays/Dual IOA with Write Cache/Opt Ext SAS port IBM Front IBM Bezel for 18-Bay BackPlane EJUG 1 IBM 12-core Typical 3.4 to 3.9 Ghz (max) EP1G 2 POWER9 Processor IBM One Processor Core Activation for #EP1G EP4G 24 IBM 16 GB DDR4 Memory EM62 16 IBM PCIe2 4-port 1GbE Adapter 5899 1 IBM PCIe2 4-Port (10Gb+1GbE) SR+RJ45 Adapter EN0S 2 IBM PCIe3 NVMe carrier card w/2 M.2 module slots EC59 1 IBM Mainstream 400GB SSD NVMe M.2 module ES14 1 ------------------------------------DB SUT------------------------------------ Supplier Description Product # Qty -------- ------------------------------------------- ---------------- --- IBM IBM Power S924 Model 42A 9009-42A 1 IBM AC Power Supply - 1400W for Server EB2M 4 (200-240 VAC) IBM Rack Indicator, Rack #1 4651 1 IBM Power Cord 4.3m (14-ft), Drawer to IBM PDU 6458 4 (250V/10A) IBM Language Group Specify - US English 9300 1 IBM Primary OS - Linux 2147 1 IBM Linux Partition Specify 0266 1 IBM PowerVM Enterprise Edition 5228 16 IBM Expanded Function Storage Backplane EJ1D 1 18 SFF-3 Bays/Dual IOA with Write Cache/Opt Ext SAS port IBM Front IBM Bezel for 18-Bay BackPlane EJUG 1 IBM 8-core Typical 3.8 to 4.0 Ghz (max) EP1E 2 POWER9 Processor IBM One Processor Core Activation for #EP1E EP4E 16 IBM 16 GB DDR4 Memory EM62 16 IBM PCIe2 4-port 1GbE Adapter 5899 1 IBM PCIe2 4-Port (10Gb+1GbE) SR+RJ45 Adapter EN0S 1 IBM PCIe3 16 Gb 2-port Fibre Channel adapter EN0A 1 IBM SAN Load Source Specify 0837 1 ----------------------------------Storage HW---------------------------------- Supplier Description Product # Qty -------- ------------------------------------------- ---------------- --- IBM FlashSystem 900 1 IBM FC Host Interface Card AF15 2 IBM 16Gb FC 4 Port Host Optics AF19 2 IBM 2.9TB IBM MicroLatency Module AF24 12 -------------------------------SAN Switch------------------------------------- Supplier Description Product # Qty -------- ------------------------------------------- ---------------- --- IBM IBM 2498-F48 SAN48B-5 48-PORT 1 16Gb Fibre Channel SAN Switch IBM 16Gb SW SFP & switch bundle 2648 1 IBM 16Gbps SW SFP single 2602 24 ------------------------------Network Switch---------------------------------- Supplier Description Product # Qty -------- ------------------------------------------- ---------------- --- IBM System Networking RackSwitch G8264 A1AC 1 IBM 10A/250V C13 to NEMA 6-15P 2.8m line cord A1RF 2 IBM SFP+ SR Transceiver 5053 48 ... Software: IBM WebSphere Application Server Liberty Core D0ZDZLL 24* 19.0.0.3 Lic+SW Maint 12 Months IBM WebSphere Application Server Liberty Core E0HGKLL 48 19.0.0.3 SW Maint Rnwl 1 Anniv IBM DB2 Advanced Enterprise Server Edition D0GB4LL 16* 11.1.4.4 Lic+SW Maint 12 Months IBM DB2 Advanced Enterprise Server Edition E0AJ4LL 32 11.1.4.4 SW Maint Rnwl 1 Anniv * Note: Pricing is based on Processor Value Units (PVU) Each AppServer and Database core is 70 PVU. |
Other Benchmark Information |
---|
DNS round robin load balancing was used and hosted on the database machine Load balancing network connectivity was 1Gbps all other connections were 10Gbps |
General Notes |
---|
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.orgCopyright © 2009-2019 Standard Performance Evaluation Corporation