6.1 and 6.0 performance with Oracle s JD Edwards EnterpriseOne 8.12 on IBM Power Systems with IBM i........ Gerrie Fisk IBM Oracle ICC June 2008 Copyright IBM Corporation, 2008. All Rights Reserved. All trademarks or registered trademarks mentioned herein are the property of their respective holders
Table of contents Change history...1 Executive summary...2 Introduction...2 Test environment...2 Test results comparing 6.0 and 6.1...3 Conclusions...5 Customer Notes...5 Appendix A Test system specifications...6 Appendix B - Resources...7 Trademarks and special notices...9
Change history Version Date Editor Editing description 1.0 06/16/08 Patrick Moore Original version 1
Executive summary In May 2008, Oracle officially announced support for Application Server 6.1 with JD Edwards EnterpriseOne software on IBM Power Systems platform with IBM i. 6.1 uses a Java implementation called IBM Technology for Java (IT4J) which is based on the same technology that IBM uses on other system platforms. IT4J provides a 32-bit implementation which can offer both performance improvements and reduced memory requirements for many applications. Customers now have a choice to run either 6.0 Classic 64-bit or 6.1 IT4J 32-bit with JD Edwards EnterpriseOne software. The IBM Oracle International Competency Center (ICC) executed tests to compare the performance of 6.1 with 6.0 in a JD Edwards EnterpriseOne 8.12 environment on an IBM Power Systems platform with i. The tests, utilizing Oracle s robust Day in the Life (DIL) kit for web users, clearly showed the benefits of upgrading to 6.1: 6.1 required up to 66% less memory than 6.0 while using up to 26% less CPU, and achieved up to 11% faster response time. Introduction To characterize the performance of 6.0 running JD Edwards EnterpriseOne software, the ICC first ran tests establishing recommended sizing guidelines and validating balanced performance across CPU, memory and disk. These tests were then repeated after switching to 6.1 to analyze its performance and memory utilization for comparison. An advantage of testing with Oracle s DIL kit is that its 17 test scripts exercise representative transactions of the most popular JD Edwards EnterpriseOne applications including Supply Chain Management, Supplier Relationship Management, Human Capital Management, Customer Relationship Management, and Financial Management. Also, this complex mixture of applications includes Advanced Pricing, Verity and Vertex to more closely reflect customer environments. Test environment A Power Systems p5-570 three-way server running i was set up for the tests as an All-on-i configuration, meaning it ran all three JD Edwards EnterpriseOne application components: the JD Edwards EnterpriseOne application server the Web tier consisting of, JD Edwards EnterpriseOne HTML, and IBM HTTP servers and the database server. 2
JD Edwards EnterpriseOne was configured with fifteen users per call object kernel. Memory was allocated into four memory pools in order to focus on and measure utilization of the web tier : *machine *base for the database functions (QSQSRVR jobs) *shrpool1 for JD Edwards EnterpriseOne server jobs *shrpool2 for the web tier. For the three different user counts of 100, 200 and 300 web users, all tests were run with JD Edwards EnterpriseOne HTML server configured as a single JVM. The white paper - IBM System i Performance and Tuning Tips for Oracle s JD Edwards EnterpriseOne 8.12, 6.0, and 6.1 was followed for the initial settings. Initial heap size for 6.0 was established at 1.5 MB of memory per user and *NOMAX was used for the maximum heap size. For 6.1 the initial heap was set to 436 MB of memory and the maximum heap was set to 1,744 MB memory. The size of the memory pool for 6.0 was also established based on the white paper. For 6.1 the size of the memory pool was rounded up from the maximum heap to 2 GB memory. A free tool new to the System i, IBM Support Assistant (ISA), was used to analyze maximum heap size and garbage collection activity for the 6.1 IT4J environment. The Power Systems server was up-to-date with the latest InfoAPAR list of IBM-recommended fixes. For IBM links to the white paper, the ISA tool, and the InfoAPAR please see Appendix B. The specifications for the Power Systems hardware used for the tests are listed in Table 3 and the software levels used are listed in Table 4 in Appendix A. Test results comparing 6.0 and 6.1 As shown in Table 1, the three different tested user counts are listed with performance metrics for 6.0 runs followed by 6.1 runs. Total web user average response time is followed by the memory allocated for the web tier memory pool, and then the percent of CPU utilized by the web tier. Also listed is the percent improvement realized by the 6.1 tests for memory and CPU. As the user count increases, the reduction in 6.1 s memory utilization improves also. For 100 users, response time with 6.1 was 3% faster while it used 33% less memory and improved CPU utilization by 33%. With 200 users, response time improved by 17% and CPU utilization improved by 23%, all while 6.1 used 50% less memory. The 300 user tests achieved 11% improvement in response time while using 26% less CPU, with 6.1 only using 2 GB memory as compared with 6 GB memory for 6.0, a 66% reduction in memory. The non-database page faults per second in the web tier memory pool remained at two or lower during all of the 6.0 and 6.1 tests, indicating memory was sufficient. 3
# of DIL kit web users Version of Application Server Total average response time (seconds) % Improvement in average response time web tier memory pool (GB) % less memory with 6.1 web tier CPU % % CPU improvement with 6.1 100 200 300 6.0 0.67 3.0 3.9 6.1 0.65 3% 2.0 33% 2.6 33% 6.0 0.91 4.0 7.7 6.1 0.75 17% 2.0 50% 5.9 23% 6.0 1.07 6.0 12.2 6.1 0.95 11% 2.0 66% 9.0 26% Table 1 JD Edwards EnterpriseOne web user testing results on the Power Systems platform with i comparing 6.0 and 6.1 Table 2 below summarizes the total throughput of the All-on-i tests by listing the total system memory allocated for the 100, 200, and 300 user tests and the total CPU % utilization for the three user counts. At all three user counts, total system performance was improved with 6.1. # of DIL kit web users Version of Application Server Total system memory used (GB) All-on-i Total % less memory with 6.1 Total All-on-i system CPU % Total % CPU improvement with 6.1 100 200 300 6.0 12.2 12.0 6.1 11.2 8% 10.5 12.5% 6.0 19.9 24.6 6.1 17.9 10% 22.0 10.5% 6.0 28.5 39.2 6.1 24.5 14% 35.1 10.5% Table 2 JD Edwards EnterpriseOne web user total system testing results on the Power Systems platform with i 4
Conclusions 6.1 outperformed 6.0 while running a JD Edwards EnterpriseOne web user workload using Oracle s DIL test kit by utilizing up to 66% less memory and consuming up to 26% less CPU while achieving up to 11% faster response time. Customer Notes While both IBM and Oracle encourage customers to upgrade to 6.1 to take advantage of these improvements, customers need to comply with Oracle s Minimum Technical Requirements (MTRs) for JD Edwards EnterpriseOne software when deciding between 6.0 and 6.1. The Oracle web site for the MTRs can be found in Appendix B. Since each customer s environment is unique, and an upgrade to 6.1 may also necessitate an upgrade to JD Edwards EnterpriseOne software, an official upgrade sizing estimate is highly recommended. A sizing estimate can be obtained by following the instructions in the sizing questionnaire available from the IBM Hardware Sizing Questionnaires web site listed in Appendix B. 5
Appendix A Test system specifications Hardware Test system System 9406 Model 570 Processors 3 Technology Memory POWER5+ 2.2 GHz Up to 28.5 GB CPW rating 12,200 Disk Arms, capacity 45 70-GB drives, 1.4 TB RAID5 Table 3 - Hardware configuration for test system Software Levels OS version V5R4, cum 8057540 JD Edwards EnterpriseOne 8.12 application code with 8.96_C1* tools code 6.0.2.17 / 6.1.0.15 Testing tool Mercury LoadRunner 8.1 with Oracle DIL kit Table 4 - Software specifications used in lab tests *Oracle s official support for 6.1 begins with JD Edwards EnterpriseOne 8.96.3. 6
Appendix B - Resources These web sites provide useful references to supplement the information contained in this document: IBM Power Systems home page http://www.ibm.com/systems/power IBM i Information Center http://publib.boulder.ibm.com/iseries IBM System i Performance and Tuning Tips for Oracle s JD Edwards EnterpriseOne 8.12, 6.0, and 6.1 /atsmastr.nsf/webindex/wp100985 IBM Support Assistant (ISA) Tools http://www.ibm.com/software/support/isa/isa40/tools.html IBM System i5 520 with POWER5 Performance in a JD Edwards EnterpriseOne Mixed Workload Environment /atsmastr.nsf/webindex/wp100511 IBM Hardware Sizing Questionnaires http://ibm.com/erp/sizing IBM Publications Center www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi?cty=us IBM Redbooks www.redbooks.ibm.com/ IBM / Oracle InfoAPAR for JD Edwards applications http://www.ibm.com/servers/enable/site/events/jde_links.html Minimum Technical Requirements (MTRs) for JD Edwards EnterpriseOne are hosted on the Oracle Partner Connection Web site; Log in to Oracle s Partner Connection with your userid and password: https://www.peoplesoft.com/corp/en/login.jsp After signing in, either drill down through: Implement, Optimize + Upgrade Implementation Guide Supported Platforms PeopleSoft EnterpriseOne Or paste this URL: http://www.peoplesoft.com/corp/en/iou/platforms/enterpriseone.jsp Then scroll down to Minimum Technical Requirements for EnterpriseOne Tools Click on Web Servers 7
Then click on the tools release such as: EnterpriseOne Tools 8.9x Select Application Server with OS/400 (IBM iseries) 8
Trademarks and special notices Copyright. IBM Corporation 1994-2008. All rights reserved. References in this document to IBM products or services do not imply that IBM intends to make them available in every country. IBM, the IBM logo, Power Systems, and are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. Information is provided "AS IS" without warranty of any kind. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Information concerning non-ibm products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute an endorsement of such products by IBM. Sources for non-ibm list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-ibm products. Questions on the capability of non-ibm products should be addressed to the supplier of those products. All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller for the full text of the specific Statement of Direction. Some information addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance, function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here to communicate IBM's current investment and development activities as a good faith effort to help with our customers' future planning. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. Photographs shown are of engineering prototypes. Changes may be incorporated in production models. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. 9