-------------------------------------------------------------------------------- SPECjEnterprise(R)2010 Result Copyright (C) 2009-2012 Standard Performance Evaluation Corporation -------------------------------------------------------------------------------- WebSphere Application Server V8.5 on IBM System HS22 and DB2 9.7 on IBM System x3850 X5 -------------------------------------------------------------------------------- 6,295.46 SPECjEnterprise2010 EjOPS -------------------------------------------------------------------------------- Submitter: IBM Corporation SPEC license # 11 Test date: Apr-2012 -------------------------------------------------------------------------------- SUT CONFIGURATION -------------------------------------------------------------------------------- JEE Server Nodes: 1 DB Server Nodes: 1 JEE Server CPUs: 12 cores, 2 chips DB Server CPUs: 40 cores, 4 chips JEE Instances: 4 DB Instances: 1 Other SUT Components: -------------------------------------------------------------------------------- BENCHMARK SETTINGS -------------------------------------------------------------------------------- Dealer Injection Rate: 3,950 Ramp Up Time: 1,500 sec DB Load Injection Rate: 4,000 Steady State Time: 3,600 sec # of Dealer Agents: 39,500 Ramp Down Time: 300 sec # of Mfg Agents: 11,850 -------------------------------------------------------------------------------- Detailed Results -------------------------------------------------------------------------------- Dealer Transaction Mix Count Tx. Mix Failure Count Purchase 3,572,777 24.99% 0 Manage 3,572,822 24.99% 5 Browse 7,151,210 50.02% 0 Total # Dealer Transactions14,296,809 Mfg. Transaction Mix Count Tx. Mix Failure Count CreateVehicleEJB 4,186,325 50.03% 726 CreateVehicleWS 4,180,507 49.97% 876 Total # Mfg. Transactions 8,366,832 Response Times Average Standard Deviation Maximum 90th% Reqd Purchase 0.237 0.52 9.916 0.580 2.000 Manage 0.199 0.29 10.714 0.440 2.000 Browse 0.273 0.59 6.647 0.800 2.000 CreateVehicleEJB 0.114 0.29 9.020 0.175 5.000 CreateVehicleWS 0.188 0.30 8.951 0.325 5.000 Reproducibility Run (SPECjEnterprise2010 EjOPS) 6,297.82 -------------------------------------------------------------------------------- SOFTWARE PRODUCTS -------------------------------------------------------------------------------- WebSphere Application Server V8.5 Vendor: IBM Corporation Availability Date: Jun-2012 Date Passed CTS: May-2012 CTS Version: 6.0 EJB Protocol: RMI/IIOP OS Name: Novell SUSE Linux Enterprise Server 11 SP1 -------------------------------------------------------------------------------- IBM J9 VM (build 2.6, JRE 1.7.0 IBM J9 Linux x86-32) Vendor: IBM Corporation Availability Date: Jun-2012 OS Name: Novell SUSE Linux Enterprise Server 11 SP1 -------------------------------------------------------------------------------- IBM J9 VM (build 2.6, JRE 1.6.0 IBM J9 Linux x86-32) Vendor: IBM Corporation Availability Date: Jun-2011 OS Name: Novell SUSE Linux Enterprise Server 11 SP1 -------------------------------------------------------------------------------- IBM DB2 Universal JDBC Drivers (3.62.56) Vendor: IBM Corporation Availability Date: Oct-2010 OS Name: Novell SUSE Linux Enterprise Server 11 SP1 -------------------------------------------------------------------------------- DB2 9.7 FP4 Vendor: IBM Corporation Availability Date: Oct-2010 OS Name: Novell SUSE Linux Enterprise Server 11 SP1 -------------------------------------------------------------------------------- SOFTWARE CONFIGURATIONS -------------------------------------------------------------------------------- JEE Application Server JEE Product: WebSphere Application Server V8.5 JVM Product: IBM J9 VM (build 2.6, JRE 1.7.0 IBM J9 Linux x86-32) JDBC Product: IBM DB2 Universal JDBC Drivers (3.62.56) Hardware: JEE AppServer HW # of Instances: 4 Interfaces: Web Interface for the Order Domain Web Services Interface for the Supplier Domain EJB Interface for the Manufacturing Domain Web Services Interface for the Manufacturing Domain Notes / Tuning Information JVM Parameters: -Xms2048m -Xmx2048m -Xmo470m -Xmn1578m -Xss128k -Xgcpolicy:gencon -Xgcthreads3 -Xnoloa -Xshareclasses:none -Xaggressive -Xtrace:none -Xlp -Xdisableexplicitgc -Dcom.ibm.CORBA.FragmentSize=10000 -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=0 -DdisableWSAddressCaching=true -Dcom.ibm.websphere.webservices.http.connectionKeepAlive=true -Dcom.ibm.websphere.webservices.http.maxConnection=50 -Dcom.ibm.websphere.webservices.http.connectionIdleTimeout=6000 -Dcom.ibm.websphere.webservices.http.connectionPoolCleanUpTime=6000 -Dcom.ibm.websphere.webservices.http.connectionTimeout=0 Refer to files appservers/node.resources.xml, and appservers/server.xml for all server configuration and resource configuration information WebSphere Application Server APAR Fixes PM61650 PM61561 PM61599 -------------------------------------------------------------------------------- Emulator Software Config JEE Product: WebSphere Application Server V8.5 JVM Product: IBM J9 VM (build 2.6, JRE 1.7.0 IBM J9 Linux x86-32) Hardware: Load Driver & Emulator HW # of Instances: 4 Notes / Tuning Information JVM Parameters: -Xms2048m -Xmx2048m -Xss128k -Xgcpolicy:gencon -Xnoloa -Xmo512m -Xmn1536m -Xtrace:none -Xlp -DdisableWSAddressCaching=true -Xgcthreads8 -Xdisableexplicitgc -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=0 -DdisableWSAddressCaching=true -Dcom.ibm.websphere.webservices.http.connectionKeepAlive=true -Dcom.ibm.websphere.webservices.http.maxConnection=50 -Dcom.ibm.websphere.webservices.http.connectionIdleTimeout=6000 -Dcom.ibm.websphere.webservices.http.connectionPoolCleanUpTime=6000 -Dcom.ibm.websphere.webservices.http.connectionTimeout=0 -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=0 Refer to files emulator/server.xml for all server configuration and resource configuration information -------------------------------------------------------------------------------- Database Software Config DB Product: DB2 9.7 FP4 Hardware: Database Server HW # of Instances: 1 Character Set: UTF-8 Notes / Tuning Information DB2_COLLECT_TS_REC_INFO=FALSE DB2_APM_PERFORMANCE=ON DB2_KEEPTABLELOCK=CONNECTION DB2_USE_ALTERNATE_PAGE_CLEANING=ON DB2_MINIMIZE_LISTPREFETCH=YES DB2_COMM=TCPIP DIAGLEVEL 3 DFT_MON_BUFPOOL off DFT_MON_LOCK off DFT_MON_SORT off DFT_MON_STMT off DFT_MON_TIMESTAMP off DFT_MON_UOW off DFT_MON_TABLE off MAX_COORDAGENTS 350 automatic CPUSPEED -1 HEALTH_MON off SVCENAME 60004 LOGBUFSZ 4096 LOGPRIMARY 150 SOFTMAX 3000 CHNGPGS_THRESH 99 LOGFILSIZ 65535 LOGSECOND 0 NEWLOGPATH/specdata2/specdata logarchmeth1 recovery NUM_IOCLEANERS 16 AUTO_MAINT off AUTO_RUNSTATS off AUTO_TBL_MAINT off LOCKLIST 100000 MAXLOCKS 100 MINCOMMIT 1 MON_REQ_METRICS none MON_ACT_METRICS none MON_OBJ_METRICS none AUTO_STMT_STATS off using AUTO_MAINT off AUTO_RUNSTATS off AUTO_TBL_MAINT off IBMDEFAULTBP immediate size 18641355 JMS_BP immediate size 192213 JMS_IDX_BP immediate size 2500 O_ITEM, M_WORKORDER, M_INVENTORY, S_SUPPLIER volatile O_ORDERLINE, O_CUSTINVENTORY, O_ORDERS, S_PURCH_ORDER, S_PURCH_ORDERLINE append on -------------------------------------------------------------------------------- Driver Config JVM Product: IBM J9 VM (build 2.6, JRE 1.6.0 IBM J9 Linux x86-32) Hardware: Load Driver & Emulator HW # of Instances: 4 Notes / Tuning Information -Xms2048M -Xmx2048M -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=0 -Dcom.ibm.websphere.naming.jndicache.cacheobject=none -Dcom.ibm.websphere.naming.hostname.normalizer=...none... -DdisableWSAddressCaching=true -Dcom.ibm.CORBA.FragmentSize=10000 -Dcom.ibm.websphere.webservices.http.connectionKeepAlive=true -Dcom.ibm.websphere.webservices.http.maxConnection=700 -Dcom.ibm.websphere.webservices.http.connectionIdleTimeout=6000 -Dcom.ibm.websphere.webservices.http.connectionPoolCleanUpTime=6000 -Dcom.ibm.websphere.webservices.http.connectionTimeout=0 -------------------------------------------------------------------------------- HARDWARE SYSTEMS -------------------------------------------------------------------------------- JEE AppServer HW (SUT hardware) Hardware Vendor: IBM Corporation Model Name: IBM HS22 Processor: Intel Xeon X5690 (Intel Turbo Boost Technology up to 3.73GHz) MHz: 3467 # of CPUs: 12 cores, 2 chips, 6 cores/chip (12 HW threads/chip) Memory (MB): 49152 DIMM[0] Count: 12 DIMM[0] Size: 4096 L1 Cache: 32 KB I + 32 KB D on chip per core L2 Cache: 256 KB I+D on chip per core Other Cache: 12 MB I+D on chip per chip OS Vendor: Novell OS Name: Novell SUSE Linux Enterprise Server 11 SP1 Disks: 2x146GB 15K SAS Network Interface: quad port 10GBit NIC Other Hardware: # of Systems: 1 H/W Available: Apr-2011 O/S Available: May-2010 Notes / Tuning Information fs.file-max = 1048576 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.wmem_default = 30000000 net.core.rmem_max = 32554432 net.core.wmem_max = 32554432 net.core.somaxconn = 32767 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_fin_timeout = 30 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 = 20480 174760 32554432 net.ipv4.tcp_wmem = 20480 174760 32554432 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_sack = 1 vm.nr_hugepages = 8192 ulimit -n 1048576 Network Tuning: set txqueuelen 60000 Stop irqbalance. Network interrupts bound to cores corresponding to the server instances. Server instances were started using taskset, 2 instances per chip. -------------------------------------------------------------------------------- Database Server HW (SUT hardware) Hardware Vendor: IBM Corporation Model Name: IBM System X3850 X5 Processor: Intel Xeon E7-4870 (Intel Turbo Boost Technology up to 2.80GHz) MHz: 2394 # of CPUs: 40 cores, 4 chips, 10 cores/chip (20 HW threads/chip) Memory (MB): 262144 DIMM[0] Count: 64 DIMM[0] Size: 4096 L1 Cache: 32 KB I + 32 KB D on chip per core L2 Cache: 256 KB I+D on chip per core Other Cache: 12 MB I+D on chip per chip OS Vendor: Novell OS Name: Novell SUSE Linux Enterprise Server 11 SP1 Disks: 2x73GB 15K SAS Network Interface: 3 x 10GBASE-SR Other Hardware: 3xSystem Storage DS3524 Express, 72x146GB 15K SAS Disks # of Systems: 1 H/W Available: Mar-2010 O/S Available: May-2010 Notes / Tuning Information fs.file-max = 1048576 kernel.sem = 250 32000 100 128 kernel.shmall = 4294967296 kernel.shmmax = 68719476736 net.core.netdev_max_backlog = 400000 net.core.optmem_max = 30000000 net.core.rmem_default = 30000000 net.core.wmem_default = 30000000 net.core.rmem_max = 30000000 net.core.wmem_max = 30000000 net.core.somaxconn = 300000 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_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_wmem = 30000000 30000000 30000000 net.ipv4.tcp_timestamps = 0 net.ipv4.tcp_sack = 0 ulimit -n 1048576 Network Tuning: set txqueuelen 60000 -------------------------------------------------------------------------------- Load Driver & Emulator HW (non-SUT hardware) Hardware Vendor: IBM Corporation Model Name: IBM BladeCenter HS22 Processor: Xeon X5670 MHz: 2933 # of CPUs: 12 cores, 2 chips, 6 cores/chip Memory (MB): 49152 L1 Cache: 32KB(I)+32KB(D) L2 Cache: 256 I+D on chip per core Other Cache: 12 MB I+D on chip per chip OS Vendor: Novell OS Name: Novell SUSE Linux Enterprise Server 11 SP1 Disks: 2 x 146GB 15K SAS Network Interface: 1 x 10GBASE-SR Other Hardware: # of Systems: 5 H/W Available: Nov-2008 O/S Available: May-2010 Notes / Tuning Information fs.file-max = 1048576 kernel.sem = 250 32000 100 128 kernel.shmall = 4294967296 kernel.shmmax = 68719476736 net.core.netdev_max_backlog = 400000 net.core.optmem_max = 30000000 net.core.rmem_default = 30000000 net.core.wmem_default = 30000000 net.core.rmem_max = 30000000 net.core.wmem_max = 30000000 net.core.somaxconn = 300000 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_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_wmem = 30000000 30000000 30000000 net.ipv4.tcp_timestamps = 0 net.ipv4.tcp_sack = 0 net.ipv4.conf.all.arp_announce = 2 net.ipv4.conf.all.arp_ignore = 1 ulimit -n 1048576 Network Tuning: set txqueuelen 60000 -------------------------------------------------------------------------------- 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 SPEC - Benchmark run on Wed Apr 18 17:02:19 CDT 2012 by SPECjEnterprise2010 v1.02 - Result submitted on null - Report generated by SPECjEnterprise2010 Reporter v1.00 Copyright (C) 2009-2012 Standard Performance Evaluation Corporation