-------------------------------------------------------------------------------- SPECjEnterprise(R)2018 Web Profile Result Copyright (C) 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 -------------------------------------------------------------------------------- 34,517.63 SPECjEnterprise2018 WebjOPS -------------------------------------------------------------------------------- Submitter: IBM Corporation SPEC license # 11 Test date: May-2019 -------------------------------------------------------------------------------- SUT CONFIGURATION -------------------------------------------------------------------------------- Java EE Server Nodes: 1 DB Server Nodes: 1 Java EE Server CPUs: 24 cores, 2 chips DB Server CPUs: 16 cores, 2 chips Java EE Instances: 8 DB Instances: 1 Other SUT Components: DNS round robin load balancing was used and hosted on the DB SUT system Load balancing network connectivity was 1Gbps all other connections were 10Gbps -------------------------------------------------------------------------------- BENCHMARK SETTINGS -------------------------------------------------------------------------------- Injection Rate: 34,300 Ramp Up Time: 600 sec DB Load Injection Rate: 40,000 Steady State Time: 3,600 sec Ramp Down Time: 300 sec # of Insurance Agents: 30 Insurance Users (threads): 343,000 Total Concurrent Users (threads): 343,000 -------------------------------------------------------------------------------- Detailed Results -------------------------------------------------------------------------------- Insurance Transactions Mix Count Tx. Mix Failure Count JSF-AcceptQuote 1,077,011 0.87% 0 JSF-AcceptQuote+WebSocket 269,367 0.22% 0 JSF-AddVehicle 1,361,117 1.10% 0 JSF-DeleteVehicle 535,776 0.43% 0 JSF-Login 4,857,854 3.91% 0 JSF-Logout 4,585,495 3.69% 0 JSF-Register 438,765 0.35% 0 JSF-RegisterInvalid 109,960 0.09% 0 JSF-Unregister 272,689 0.22% 0 JSF-UpdateUser 545,261 0.44% 0 JSF-ViewInsurance 524,839 0.42% 0 JSF-ViewQuote 1,361,235 1.10% 0 JSF-ViewUser 817,074 0.66% 0 JSF-ViewVehicle 1,871,261 1.51% 0 REST-AcceptQuote 6,106,264 4.91% 0 REST-AcceptQuote+WebSocket 1,523,978 1.23% 0 REST-AddVehicle 7,719,969 6.21% 0 REST-DeleteVehicle 3,053,041 2.46% 0 REST-Login 27,553,374 22.17% 0 REST-Logout 26,007,554 20.93% 0 REST-Register 2,488,783 2.00% 0 REST-RegisterInvalid 621,685 0.50% 0 REST-Unregister 1,546,013 1.24% 0 REST-UpdateUser 3,089,367 2.49% 0 REST-ViewInsurance 2,970,937 2.39% 0 REST-ViewQuote 7,720,337 6.21% 0 REST-ViewUser 4,632,233 3.73% 0 REST-ViewVehicle 10,602,214 8.53% 0 Total # transactions 124,263,453 Response Times Average Standard Deviation Maximum 90th% Reqd JSF-AcceptQuote 0.205 0.23 2.752 0.490 2.000 JSF-AcceptQuote+WebSocket 0.271 0.32 3.682 0.610 2.000 JSF-AddVehicle 0.235 0.21 2.584 0.450 2.000 JSF-DeleteVehicle 0.107 0.14 1.687 0.250 2.000 JSF-Login 0.149 0.25 3.404 0.400 2.000 JSF-Logout 0.038 0.07 1.199 0.110 2.000 JSF-Register 0.370 0.72 7.822 1.030 2.000 JSF-RegisterInvalid 0.472 0.93 9.733 1.300 2.000 JSF-Unregister 0.094 0.15 1.641 0.240 2.000 JSF-UpdateUser 0.187 0.27 3.056 0.450 2.000 JSF-ViewInsurance 0.089 0.14 1.627 0.220 2.000 JSF-ViewQuote 0.175 0.26 3.067 0.430 2.000 JSF-ViewUser 0.099 0.14 1.668 0.240 2.000 JSF-ViewVehicle 0.094 0.13 1.677 0.230 2.000 REST-AcceptQuote 0.183 0.23 3.895 0.470 2.000 REST-AcceptQuote+WebSocket 0.248 0.29 4.333 0.590 2.000 REST-AddVehicle 0.113 0.14 2.449 0.250 2.000 REST-DeleteVehicle 0.094 0.14 3.010 0.240 2.000 REST-Login 0.037 0.07 1.804 0.110 2.000 REST-Logout 0.000 0.00 0.168 0.010 2.000 REST-Register 0.042 0.07 1.781 0.120 2.000 REST-RegisterInvalid 0.138 0.27 4.217 0.390 2.000 REST-Unregister 0.053 0.08 1.680 0.140 2.000 REST-UpdateUser 0.088 0.13 2.374 0.230 2.000 REST-ViewInsurance 0.040 0.07 1.751 0.110 2.000 REST-ViewQuote 0.085 0.13 2.391 0.220 2.000 REST-ViewUser 0.044 0.07 1.768 0.120 2.000 REST-ViewVehicle 0.040 0.07 1.773 0.110 2.000 Reproducibility Run (SPECjEnterprise2018 WebjOPS) 34,524.96 -------------------------------------------------------------------------------- SOFTWARE PRODUCTS -------------------------------------------------------------------------------- WebSphere Liberty Core 19.0.0.3 Vendor: IBM Corporation Availability Date: Apr-2019 Date Passed CTS: Jun-2018 CTS Version: 8.0 OS Name: SUSE Linux Enterprise Server 12 SP4 -------------------------------------------------------------------------------- IBM SDK, Java Technology Edition, Version 8, Service Refresh 5, Fixpack 30 Vendor: IBM Corporation Availability Date: Mar-2019 OS Name: SUSE Linux Enterprise Server 12 SP4 -------------------------------------------------------------------------------- IBM DB2 Universal JDBC Drivers (4.25.13) Vendor: IBM Corporation Availability Date: Nov-2018 OS Name: SUSE Linux Enterprise Server 12 SP4 -------------------------------------------------------------------------------- DB2 11.1 Mod 4 Fix Pack 4 Vendor: IBM Corporation Availability Date: Nov-2018 OS Name: SUSE Linux Enterprise Server 12 SP4 -------------------------------------------------------------------------------- SOFTWARE CONFIGURATIONS -------------------------------------------------------------------------------- Insurance Java EE Configuration Java EE Product: WebSphere Liberty Core 19.0.0.3 JVM Product: IBM SDK, Java Technology Edition, Version 8, Service Refresh 5, Fixpack 30 Database Driver Product:IBM DB2 Universal JDBC Drivers (4.25.13) Hardware: Java EE Web Profile Application Server HW # of Instances: 6 Interfaces: Web (JSF and REST) Interface for the Insurance service Notes / Tuning Information Java Version: Java(TM) SE Runtime Environment (build 8.0.5.30 - pxl6480sr5fp30-20190207_01(SR5 FP30)) JVM Parameters (refer to file insurance/jvm.options): -Xlp -Xms8g -Xmx8g -Dhttp.keepAlive=true -Dhttp.maxConnections=2000 -Xgcthreads24 -Xconcurrentlevel0 -Xaggressive -Xss128k -Xtrace:none -Xshareclasses:none -Dcom.ibm.websphere.ejbcontainer.poolSize=insurance#insurance.war#InsuranceAgentsService=H60,1000:insurance#insurance.war#PolicyVehicleService=H60,1000: insurance#insurance.war#PolicyHolderRegistration=H60,1000:insurance#insurance.war#PolicyHolderService=H60,1000 -Xdisableexplicitgc -Xmn6g -Xgc:tlhMaximumSize=524288,tlhIncrementSize=16384 -Dcom.ibm.crypto.plus.provider.DISABLEHMAC=true -XlockReservation Refer to file insurance/server.xml for all server configuration and resource configuration information The IBMJCEPlus crypto provider is enabled in the /jre/lib/security/java.security file (see config/jre/lib/security), adding it in as the number 1 in the security.provider list: security.provider.1=com.ibm.crypto.plus.provider.IBMJCEPlus -------------------------------------------------------------------------------- Insurance Provider Java EE Configuration Java EE Product: WebSphere Liberty Core 19.0.0.3 JVM Product: IBM SDK, Java Technology Edition, Version 8, Service Refresh 5, Fixpack 30 Database Driver Product:IBM DB2 Universal JDBC Drivers (4.25.13) Hardware: Java EE Web Profile Application Server HW # of Instances: 1 Interfaces: REST Interface for the Insurance provider service Notes / Tuning Information Java Version: Java(TM) SE Runtime Environment (build 8.0.5.30 - pxl6480sr5fp30-20190207_01(SR5 FP30)) JVM Parameters (refer to file insurance-provider/jvm.options): -Xlp -Xms2250m -Xmx2250m -Dhttp.keepAlive=true -Dhttp.maxConnections=2000 -Xgcthreads24 -Xaggressive -Xss128k -Xtrace:none -Xshareclasses:none -Dcom.ibm.websphere.ejbcontainer.poolSize=insurance-provider#insurance-provider.war#VehicleService=H60,1000: insurance-provider#insurance-provider.war#ActuarialService=H60,1000:insurance-provider#insurance-provider.war#AgentManager=H60,1000 -Xdisableexplicitgc -Xmn1365m -Xgc:tlhMaximumSize=524288,tlhIncrementSize=16384 -Dcom.ibm.crypto.plus.provider.DISABLEHMAC=true -XlockReservation Refer to file insurance-provider/server.xml for all server configuration and resource configuration information The IBMJCEPlus crypto provider is enabled in the /jre/lib/security/java.security file (see config/jre/lib/security), adding it in as the number 1 in the security.provider list: security.provider.1=com.ibm.crypto.plus.provider.IBMJCEPlus -------------------------------------------------------------------------------- Vehicle Java EE Configuration Java EE Product: WebSphere Liberty Core 19.0.0.3 JVM Product: IBM SDK, Java Technology Edition, Version 8, Service Refresh 5, Fixpack 30 Database Driver Product:IBM DB2 Universal JDBC Drivers (4.25.13) Hardware: Java EE Web Profile Application Server HW # of Instances: 1 Interfaces: REST Interface for the Vehicle service Notes / Tuning Information Java Version: Java(TM) SE Runtime Environment (build 8.0.5.30 - pxl6480sr5fp30-20190207_01(SR5 FP30)) JVM Parameters (refer to file vehicle/jvm.options): -Xlp -Xms2250m -Xmx2250m -Xgcthreads24 -Xaggressive -Xss128k -Xtrace:none -Xshareclasses:none -Dcom.ibm.websphere.ejbcontainer.poolSize=vehicle#vehicle.war#VehicleService=H60,1000 -Xdisableexplicitgc -Xmn1365m -Xgc:tlhMaximumSize=524288,tlhIncrementSize=16384 -Dcom.ibm.crypto.plus.provider.DISABLEHMAC=true -XlockReservation Refer to file vehicle/server.xml for all server configuration and resource configuration information The IBMJCEPlus crypto provider is enabled in the /jre/lib/security/java.security file (see config/jre/lib/security), adding it in as the number 1 in the security.provider list: security.provider.1=com.ibm.crypto.plus.provider.IBMJCEPlus -------------------------------------------------------------------------------- Database SW Configuration DB Product: DB2 11.1 Mod 4 Fix Pack 4 Hardware: Database Server HW # of Instances: 1 Character Set: UTF16 Notes / Tuning Information DB2 Registry Variables: DB2FCMCOMM=TCPIP4 DB2TCP_CLIENT_CONTIMEOUT=0 DB2TCP_CLIENT_RCVTIMEOUT=0 DB2_USE_ALTERNATE_PAGE_CLEANING=ON DB2_MINIMIZE_LISTPREFETCH=YES DB2_KEEPTABLELOCK=CONNECTION DB2_APM_PERFORMANCE=ON DB2TCPCONNMGRS=8 DB2_COLLECT_TS_REC_INFO=FALSE DB2SOSNDBUF=131072 DB2SORCVBUF=131072 DB2COMM=TCPIP DB2AUTOSTART=NO Database Manager Configuration: DIAGLEVEL=3 DFT_MON_BUFPOOL=on DFT_MON_LOCK=off DFT_MON_SORT=off DFT_MON_STMT=off DFT_MON_TIMESTAMP=on DFT_MON_UOW=off DFT_MON_TABLE=off CPUSPEED=1.889377e-07 MAX_COORDAGENTS=AUTOMATIC(10000) HEALTH_MON=off SHEAPTHRES=2000000 Database Configuration: LOGBUFSZ=4096 LOGSECOND=0 LOGPRIMARY=256 SOFTMAX=8080 CHNGPGS_THRESH=99 LOGFILSIZ=65535 AUTO_MAINT=off AUTO_RUNSTATS=off AUTO_TBL_MAINT=off SHEAPTHRES_SHR=183205 SORTHEAP=50000 NUM_IOCLEANERS=32 MAXAPPLS=2246 MAXLOCKS=100 -------------------------------------------------------------------------------- Driver Configuration JVM Product: IBM SDK, Java Technology Edition, Version 8, Service Refresh 5, Fixpack 30 Hardware: Load Driver HW # of Instances: 6 Notes / Tuning Information Java Version: Java(TM) SE Runtime Environment (build 8.0.5.30 - pxl6480sr5fp30-20190207_01(SR5 FP30)) JVM Parameters: -Xms4G -Xmx4G -Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0 -Djava.net.preferIPv4Stack=true -------------------------------------------------------------------------------- HARDWARE SYSTEMS -------------------------------------------------------------------------------- Java EE Web Profile Application Server HW (SUT hardware) Hardware Vendor: IBM Corporation Model Name: IBM Power S924 Processor: POWER9 MHz: 3400 # of CPUs: 24 cores, 2 chips, 12 cores/chip (96 HW threads/chip) Memory (MB): 262144 L1 Cache: 64 KB I + 64 KB D on chip per core L2 Cache: 512 KB I+D on chip per core Other Cache: 120 MB I+D on chip per chip shared NUCA / 12 cores OS Vendor: SUSE OS Name: SUSE Linux Enterprise Server 12 SP4 Disks: 1x 400 GB NVMe Network Interface: 4x 10GBit network ports Other Hardware: # of Systems: 1 H/W Available: Mar-2018 O/S Available: Dec-2018 Notes / Tuning Information /etc/sysctl.conf: fs.file-max = 1048576 fs.inotify.max_user_watches = 65536 kernel.sched_compat_yield = 1 kernel.sem = 250 32000 100 128 kernel.shmall = 4294967296 kernel.shmmax = 68719476736 net.core.netdev_max_backlog = 250000 net.core.optmem_max = 30000000 net.core.rmem_default = 30000000 net.core.rmem_max = 32554432 net.core.somaxconn = 32767 net.core.wmem_default = 30000000 net.core.wmem_max = 32554432 net.ipv4.conf.all.arp_announce = 2 net.ipv4.conf.all.arp_ignore = 1 net.ipv4.conf.all.promote_secondaries = 1 net.ipv4.conf.all.rp_filter = 1 net.ipv4.conf.default.accept_source_route = 0 net.ipv4.conf.default.promote_secondaries = 1 net.ipv4.conf.default.rp_filter = 1 net.ipv4.icmp_echo_ignore_broadcasts = 1 net.ipv4.ip_forward = 0 net.ipv4.ip_local_port_range = 1024 65000 net.ipv4.tcp_fin_timeout = 30 net.ipv4.tcp_keepalive_intvl = 15 net.ipv4.tcp_keepalive_probes = 5 net.ipv4.tcp_max_syn_backlog = 30000 net.ipv4.tcp_max_tw_buckets = 2000000 net.ipv4.tcp_mem = 30000000 30000000 30000000 net.ipv4.tcp_no_metrics_save = 1 net.ipv4.tcp_rmem = 20480 174760 32554432 net.ipv4.tcp_sack = 1 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_window_scaling = 1 net.ipv4.tcp_wmem = 20480 174760 32554432 vm.max_map_count = 262144 ulimit -n 1048576 -v unlimited -u 4134075 default_hugepagesz=16M echo 4096 > /proc/sys/vm/nr_hugepages Network Tuning (see config/appserver/network_adapter_tuning.sh): set txqueuelen 60000 Stop irqbalance Network interrupts Tuning (see config/appserver/network_interrupts_tuning.sh): On each interface used for driver and database communication set: arp_ignore 1 arp_announce 2 rx-usecs 100 mtu 1500 Server instances were started using numactl, binding 4 instances per NUMA node (see config/appserver/start_server.sh). Yes: The test sponsor attests, as of date of publication, that CVE-2017-5754 (Meltdown) is mitigated in the system as tested and documented. Yes: The test sponsor attests, as of date of publication, that CVE-2017-5753 (Spectre variant 1) is mitigated in the system as tested and documented. Yes: The test sponsor attests, as of date of publication, that CVE-2017-5715 (Spectre variant 2) is mitigated in the system as tested and documented. -------------------------------------------------------------------------------- Database Server HW (SUT hardware) Hardware Vendor: IBM Corporation Model Name: IBM Power S924 Processor: POWER9 MHz: 3400 # of CPUs: 16 cores, 2 chips, 8 cores/chip (64 HW threads/chip) Memory (MB): 262144 L1 Cache: 64 KB I + 64 KB D on chip per core L2 Cache: 512 KB I+D on chip per core Other Cache: 80 MB I+D on chip per chip shared NUCA / 8 cores OS Vendor: SUSE OS Name: SUSE Linux Enterprise Server 12 SP4 Disks: 1x 1000 GB RAID5 SSD Network Interface: 2x 10GBit and 1x 1GBit network ports Other Hardware: 2x 16Gb fibre channel ports; 1x IBM FlashSystem 900 # of Systems: 1 H/W Available: Mar-2018 O/S Available: Dec-2018 Notes / Tuning Information /etc/sysctl.conf: net.ipv4.ip_forward = 0 net.ipv6.conf.all.forwarding = 0 net.ipv4.icmp_echo_ignore_broadcasts = 1 net.ipv4.conf.all.rp_filter = 1 fs.inotify.max_user_watches = 65536 net.ipv4.conf.default.promote_secondaries = 1 net.ipv4.conf.all.promote_secondaries = 1 net.ipv4.conf.all.arp_filter = 1 kernel.sem = 250 256000 100 129280 fs.aio-max-nr = 1048576 fs.file-max = 6815744 kernel.shmall = 10737418240 net.core.netdev_max_backlog = 400000 net.core.optmem_max = 30000000 net.core.rmem_default = 30000000 net.core.rmem_max = 30000000 net.core.somaxconn = 40000 net.core.wmem_default = 30000000 net.core.wmem_max = 30000000 net.ipv4.ip_local_port_range = 1024 65535 net.ipv4.tcp_fin_timeout = 10 net.ipv4.tcp_max_syn_backlog = 30000 net.ipv4.tcp_max_tw_buckets = 2000000 net.ipv4.tcp_mem = 30000000 30000000 30000000 net.ipv4.tcp_rmem = 30000000 30000000 30000000 net.ipv4.tcp_timestamps = 0 net.ipv4.tcp_wmem = 30000000 30000000 30000000 vm.zone_reclaim_mode = 1 vm.swappiness = 5 ulimit -n 1048576 -v unlimited -u 4134075 Yes: The test sponsor attests, as of date of publication, that CVE-2017-5754 (Meltdown) is mitigated in the system as tested and documented. Yes: The test sponsor attests, as of date of publication, that CVE-2017-5753 (Spectre variant 1) is mitigated in the system as tested and documented. Yes: The test sponsor attests, as of date of publication, that CVE-2017-5715 (Spectre variant 2) is mitigated in the system as tested and documented. -------------------------------------------------------------------------------- Load Driver HW (non-SUT hardware) Hardware Vendor: IBM Corporation Model Name: IBM Power S824 Processor: POWER8 MHz: 3525 # of CPUs: 24 cores, 2 chips, 12 cores/chip (96 HW threads/chip) Memory (MB): 262144 L1 Cache: 32 KB I + 64 KB D on chip per core L2 Cache: 512 KB I+D on chip per core Other Cache: L3 Cache: 8 MB I+D on chip per core; L4 Cache: 128 MB per chip OS Vendor: Red Hat OS Name: Red Hat Enterprise Linux 7.6 Disks: 2x 120GB SSD Network Interface: 2x 10 GBit and 2x 1GBit network ports Other Hardware: # of Systems: 4 H/W Available: Jun-2014 O/S Available: Oct-2018 Notes / Tuning Information /etc/sysctl.conf: net.ipv4.icmp_echo_ignore_broadcasts = 1 net.ipv4.conf.all.rp_filter = 1 fs.inotify.max_user_watches = 65536 net.ipv4.conf.default.promote_secondaries = 1 net.ipv4.conf.all.promote_secondaries = 1 fs.file-max = 1048576 kernel.sem = 250 32000 100 128 kernel.shmall = 4294967296 kernel.shmmax = 68719476736 net.core.optmem_max = 30000000 net.core.rmem_default = 30000000 net.core.wmem_default = 30000000 net.ipv4.conf.all.arp_announce = 2 net.ipv4.conf.all.arp_ignore = 1 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.default.accept_source_route = 0 net.ipv4.ip_forward = 0 net.ipv4.ip_local_port_range = 1024 65000 net.ipv4.tcp_max_syn_backlog = 30000 net.ipv4.tcp_max_tw_buckets = 2000000 net.ipv4.tcp_mem = 30000000 30000000 30000000 kernel.sched_compat_yield = 1 net.core.somaxconn = 32767 net.core.netdev_max_backlog = 250000 net.ipv4.tcp_fin_timeout = 30 net.ipv4.tcp_keepalive_intvl = 15 net.ipv4.tcp_keepalive_probes = 5 net.core.rmem_max = 32554432 net.core.wmem_max = 32554432 net.ipv4.tcp_rmem = 20480 174760 32554432 net.ipv4.tcp_wmem = 20480 174760 32554432 net.ipv4.tcp_window_scaling = 1 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_sack = 1 net.ipv4.tcp_no_metrics_save = 1 kernel.pid_max = 229376 ulimit -n 1048576 -v unlimited -u 4134075 -------------------------------------------------------------------------------- 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 SPEC - Benchmark run on Thu May 09 15:46:50 CDT 2019 by SPECjEnterprise2018 Web Profile v1.0.0 - Result submitted on May 10, 2019 - Report generated by SPECjEnterprise2018 Web Profile Reporter v1.0 Copyright (C) 2009-2019 Standard Performance Evaluation Corporation