E-BUSINESS SUITE APPLICATIONS R12 (R12.1.2) ORDER- TO-CASH (BATCH) BENCHMARK - USING ORACLE DATABASE 11g ON AN IBM Power 730 SERVER

Transcription

1 O RACLE E-BUSINESS B ENCHMARK R EV. 1.0 E-BUSINESS SUITE APPLICATIONS R12 (R12.1.2) ORDER- TO-CASH (BATCH) BENCHMARK - USING ORACLE DATABASE 11g ON AN IBM Power 730 SERVER As a global leader in e-business applications, Oracle is committed to delivering high performance solutions that meet our customers expectations. Business software must deliver rich functionality with robust performance. This performance must be maintained at volumes that are representative of customer environments. Oracle benchmarks demonstrate our software s performance characteristics for a range of processing volumes in a specific configuration. Customers and prospects can use this information to determine the software, hardware, and network configurations necessary to support their processing volumes. The primary objective of our benchmarking effort is to provide as many data points as possible to support this important decision. SUMMARY OF RESULTS This batch benchmark test was run on a 12-core server. 100,000 Order/Inv. Lines Batch Workload Threads Time (Min) Hourly Order Line Throughput HVOP ,390,243 Pick Release ,017 Ship Confirm ,000,000 Interface Trip Stop ,315,789 Inventory ,083,333 Auto Invoice ,489 Revenue Recognition 7,200,000 Accounting Submit ,000,000 Accounting Create ,750 Parent Proc Total: ,399 Wall Clock Duration* ,296 More processes are included in this summary than were reported in either or 11i. Consequently, these results cannot be compared to earlier releases. Note that the hourly throughput numbers mentioned above are linear extrapolations. Many factors can influence performance and your results may differ. * The Wall Clock Duration includes all of the job scheduling and management activity (parent process) as well as some idle intervals due to polling or waiting for all workers in a particular process to complete prior to kicking off the subsequent process. These intervals would not increase substantially, if at all, as the workload size is increased. Consequently, the throughput for larger workloads would converge towards the Parent Process Total: value. BENCHMARK PROFILE In September 2011, Oracle and IBM conducted a benchmark in Beaverton, OR to measure the batch performance of the Oracle E-Business Standard Benchmark processes in an environment running Oracle E-Business Suite R12 (12.1.2) with Oracle11g database ( ) for the AIX operating system on a single IBM Power 730 (POWER7 ) Express Server configured with two six-core processors (12-cores total), running AIX 6.1 TL04 (64-bit) OS. A single IBM Storwize V7000 disk array was used for storage. The benchmark measured the Order Management batch business process hourly throughputs for a large database model. Testing was conducted in a controlled environment with no other applications running. The goal of this Benchmark was to obtain reference batch throughputs for Oracle E-Business Suite R12 Benchmark on an IBM Power 730 server running AIX. COPYRIGHT 2011 Oracle, Inc. All rights reserved. Page - 1

2 BENCHMARK METHODOLOGY E-Business Suite R12 Benchmark batch processes are initiated from a benchmark-provided SQL script. The batch workloads were run as standard concurrent processes via the concurrent manager. BENCHMARK BUSINESS PROCESSES This E-Business Suite benchmark consists of a batch flow with seven metered processes. Batch Order-to-Cash Processes Figure 2 shows the configuration used for this benchmark run. Business Process Number of Threads Used Power 730 DB Server & Apps Server 12-core 48 GB 58% Utilized Storwize V7000 HVOP 24 (24) Pick Release 24 (24) Interface Trip Stop 24 (24) Inventory 24 (500) Auto Invoice 24 (24) Revenue Recognition 24 (15) Accounting Processes 24 (4) Note that while 24 threads (workers) were entered at setup, the actual number of child processes spawned may have been larger (Inventory) or smaller (Revenue Recognition and Accounting). 4 Drawers Data HVOP Pick Release Order Ship Order 1 Drawer Logs Interface Trip Stop AutoInvoice Revenue Recognition Xfer to GL / Journal Import GL Autopost Figure 2: 2-Tier Configuration This benchmark was run as a Physical 2-Tier configuration with a single machine hosting both the Database and Application server instances on a single OS image. Figure 3: Order-to-Cash Process Flow High Volume Order Processing (HVOP): The HVOP program processes orders by reading the rows from the Order Management Interface tables and converting the interface records into permanent order headers and their respective order lines. The orders are then booked and advanced to the shipping state. Pick Release (and Ship Confirm): Pick Release finds and releases the eligible delivery lines that meet the release criteria, and creates move orders. The process of transacting move orders creates a reservation and determines the inventory source sub-inventory. Ship Confirm is the process of confirming that items have shipped. When a delivery is ship-confirmed, Shipping Execution confirms that the delivery lines associated with the delivery have shipped. COPYRIGHT 2011 Oracle, Inc. All rights reserved. Page - 2

3 Batch Order-to-Cash Processes Continued Interface Trip Stop: The deliveries created in the previous step are then assigned to trips, which may involve multiple stops depending upon the shipping addresses of the deliveries. SRS has been modified to accept Organization code as a parameter and process the trip stops for the specified organization. Interface Trip Stop - SRS has also been enhanced to spawn multiple child processes to process trip stops in parallel. The parameter Stops per Batch is used to specify the number of stops to be processed by each thread of the Interface Trip Stop - SRS. Interface Trip Stop - SRS has also been enhanced to defer the Inventory Interface processes. In the E-Business Suite kit, this profile is set to Yes so that the Inventory Interface transactions are processed in the background by the Inventory transaction manager. INV Material: The material transaction manager is configured to execute material transaction by periodic concurrent request submissions and by direct submission of multiple transaction managers via the benchmark SQL script. The execution interval is set to 5 minutes. Auto-Invoice: The Auto-Invoice process is used to import invoices, credit memos, debit memos, and on account credits. Receivables ensures that the data imported is accurate and valid. Revenue Recognition: Revenue Recognition program generates the revenue distribution records for the invoices and credit memos that use Invoicing and Accounting Rules. Accounting rules were assigned to recognize revenue over a 12-month accounting period. The Revenue Recognition program will create distribution records for the invoices and credit memos that are created in Receivables and imported using Auto-Invoice. Transfer to General Ledger & Journal Import: The General Ledger Interface program transfers Receivables transaction accounting distributions to the general ledger interface table (GL_INTERFACE) and creates either detailed or summarized journal batches. Receivables creates un-posted journal entries in general ledger and executes Journal Import from Oracle General Ledger. It posts journal batches in Oracle General Ledger to update account balances. BENCHMARK RESULTS Batch Business Metrics Achieved Output Order to Cash Number of Order Lines Created/Booked 100,000 Number of Order Lines Picked 100,000 Number of Order Lines Ship Confirmed 100,000 Number of Order lines Interface Trip 100,000 Stopped Number of Invoice Headers Created 100,000 Number of Invoice Lines Created 200,000 Table 1: Batch Transactions Completed 100,000 order lines were processed in this test. Table 2 shows the processing time in minutes. 100,000 Order/Inv. Lines Batch Workload Threads Time (Min) Hourly Order Line Throughput HVOP ,390,243 Pick Release ,017 Ship Confirm ,000,000 Interface Trip Stop ,315,789 Inventory ,083,333 Auto Invoice ,489 Revenue Recognition 7,200,000 Accounting Submit ,000,000 Accounting Create ,750 Parent Proc Total: ,399 Wall Clock Duration* ,296 Table 2: Order-to-Cash (24 Worker) Batch Performance R Application changes, data model additions and test methodology improvements render direct comparison to previous Oracle E-Business release , and results invalid. General Ledger Auto-post: This posts journal batches to update the account balances of the detail and summary accounts. It can post actual budget or encumbrance journal batches. COPYRIGHT 2011 Oracle, Inc. All rights reserved. Page - 3

4 SERVER PERFORMANCE Figure 4 shows the average CPU utilization on the server. The value shown is the average across the processors (12 cores total, 24 vcpus). Note that the sampling rate yielded few data points to average for the briefest processes. % Average CPU Utilization E-Business R12 Order-to-Cash Batch using Oracle11g on an IBM Power 730 Database and Application Server Workload % User % System % I/O Wait % Idle HVOP Pick Release Pick Release Ship Confirm Interface Trip Stop Inventory Auto Invoice Rev. Recognition Submit Accounting Create Accounting Wall Clock Avg Table 3: Average CPU Utilization Breakout (24 Workers) Only 2 Huge Pages (32GB) were used. Figure 4: Average DB/App/Web CPU Utilization Average GB Used DB/App Server O-to-C 38 GB Running CPU Order-to-Cash Batch Figure 5: Running CPU Utilization Table 4: Average Memory Utilization I/O PERFORMANCE A V7000 storage system equipped with five disk drawers was used for storage. The batch workload requires optimal I/O performance. I/O Performance O-to-C preads/sec Avg 27 Peak 295 pwrites/sec Avg 645 Peak 4,980 Reads Kbs/Sec Avg 438 Peak 7,844 WritesKbs/Sec Avg 23,544 Peak 82,273 I/O/Sec Avg 700 Peak 5,064 Table 5: Average I/O Utilization Breakout COPYRIGHT 2011 Oracle, Inc. All rights reserved. Page - 4

5 DATA COMPOSITION DESCRIPTION Major data components for the model under test are summarized in the following table. Application Business Objects Large/Extra- Large Model TCA Organizations 1,100,000 Contacts 4,900,000 Contact Points 3,700,000 Accounts 1,100,000 Account Sites 1,090,000 Account Site Uses 2,180,000 Contracts Contracts 222,000 Install Base Instances 1,300,000 Trackable Items 5 Items 1,100,000 HR Managers 800 Employees 250,000 Payroll Users 250,000 Users 20,000 Credit Card 4,000,000 Entries Supplier(s) 10,000 PATCHES The following patches were applied to the benchmark environment on top of Oracle E-Business Suite R12 (12.1.2). 1. Oracle E-Business Applications R12 (12.1.2) DB: Oracle 11g Examples CD Note: quite a few from the above list are due to Database import requirements. If import is not performed, the importrelated patches need not be applied. Assets Asset Categories 984 General Ledger GL Code 93,417 Combinations Table 7: Data Composition COPYRIGHT 2011 Oracle, Inc. All rights reserved. Page - 5

6 APPLICATION TUNING Database: APP: (Quantum 2.9.9) (Quantum Data patch) Application Tuning: Please refer to Jinsoo's performance page for all the Order to Cash index tuning recommendations. It was already included in the database that was being imported from Linux. Decreased the poll interval and worker wait time for the Revenue Recognition and Accounting job steps OPERATING SYSTEM TUNING AIX TUNING SMT-2 thread : smtctl -t 2 Memory prefetch disable: : dscrctl -n -s 1 "capabilities=cap_propagate,cap_bypass_rac_v MM" a12 : bosboot -ad /dev/ipldevice : initvis.ora: lock_sga=true Multipage enable: DB: export LDR_CNTRL=DATAPSIZE=64K@TEXTPSIZE=64K@S TACKPSIZE=64K APP: export LDR_CNTRL=DATAPSIZE=64K@TEXTPSIZE=64K@S TACKPSIZE=64K@MAXDATA=0xA @DSA Maximum number of processes adjustment: eg. smitty System Environments Change/Show Characteristics of Operating System: update Maximum number of PROCESSES allowed per_user [99999] ARG/ENV list size in 4K byte blocks [256] DATABASE OPERATING SYSTEM TUNING /etc/security/limits: (DB user and APPs user) : fsize = -1 : core = : cpu = -1 : data = -1 : rss = -1 : stack = -1 : nofiles = -1 : stack_hard = -1 : data_hard = -1 Huge pages were enabled for Database instance COPYRIGHT 2011 Oracle, Inc. All rights reserved. Page - 6

7 BENCHMARK ENVIRONMENT HARDWARE CONFIGURATION An IBM Power 730 Express Server (8231-E2B) was used for the database and application/web server. It was equipped with the following: 2 6-Core 3.72 GHz with IBM POWER7 two six-core processor chips (12 cores total) (two-threaded SMTenabled), each with L2 Cache of 256 KB per core and 4 MB L3 cache per core. Intelligent Energy Optimization has been deployed with setting for maximum performance. (3,920 MHz reported for this test) Total Memory: 48 GB (~38 GB peak) Network: Gigabit full duplex. Operating system: IBM AIX 6.1 TL Storage: V7000 with 5 drawers of 6.5 TB each (Total 32.5 Terabytes.). Each drawer has 24 physical disks --- RAID 0, two controllers - one exclusively for redo logs. SOFTWARE VERSIONS Oracle s E-Business Suite (E-Business Suite Kit) R Oracle11g (64-bit) IBM AIX 6.1 TL (on the database and Application /Web/CM servers) The following Java versions have all been used in the Oracle Apps environment: : Java 6 SR8 FP1 : Java 5 SR12 FP1 : Java SR13FP9 Glossary and Acronyms: ATP Available to Promise BEE Batch Element Entries HVOP High Volume Order Processing OASB Oracle Applications Standard Benchmark RAC Real Applications Clusters For more details on IBM Power 730, please visit 03.ibm.com/systems/power/hardware/730/index.html For more details on IBM Storwize v7000, please visit 03.ibm.com/systems/storage/disk/storwize_v7000/index.html COPYRIGHT 2011 Oracle, Inc. All rights reserved. Page - 7

8 Oracle Applications Performance & Benchmarks 500 Oracle Parkway Redwood Shores, California Tel 650/ Fax 650/ World Wide Web The results published in this report have been independently reviewed and audited by: E-Business R12 Order to Cash Batch September 2011 Audit Approved November 13, 2011 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA U.S.A. Worldwide Inquiries: Phone: Fax: Copyright 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd oracle.com 2011 IBM, Inc. All rights reserved. IBM, the IBM logo, AIX, POWER7 and TotalStorage are trademarks or registered trademarks of IBM, Inc. in the United States and other countries. COPYRIGHT 2011 Oracle, Inc. All rights reserved. Page - 8