Post GoingLive Sizings

Performance & Information Lifecycle Management SAP AG

Different Times, Different Phases, Different Goals of Sizing

Sizing takes place in different phases of a project
Go Live

Project Preparation

Business Blueprint

Realization

Final Preparation

Going Live & Support

1. Very early to plan hardware expenditures 2. A few months before live start to verify assumptions Determine the overall performance requirements

Upgrade

Migration

Business Units

Functional Changes

3. During production stages to ensure operations and verify/adjust estimations made earlier. Trigger events include: Upgrade database, operating system, SAP application Reconfigure system landscape Change business process Rollouts: more users or other load

SAP 2009 2

Introduction Sizing Approaches on Production Data

Assumptions
The system is properly tuned for optimal performance The focus is on net consumption of business processes on the hardware
CPU Memory Disk Network load between application server and front end, between two servers

Capacity planning motivation is the same minimize the impact on end user productivity and its associated costs Note: Resource consumption (CPU, memory) strongly depends on Business process: customizing, customer extensions Combination of hardware and software: configurations Recommendations refer to used resources, not allocated ones Re-Sizing
All projects SAP system monitors Goal: Extend an existing system by load E.g. by volume 100 additional users who'll do the same as the current productive ones
SAP 2009 3

Delta Sizing
All projects SAP system monitors Goal: Extend an existing system by functions By different functions, e.g. you are live with CRM and want to add SCM

Upgrade Sizing
All projects SAP system monitors SAP Notes Goal: Upgrade SAP software

Different procedures according to goals

Re-Sizing: add the load coming in through the additional users and projects causing the same load structure Delta Sizing: treat like a new sizing and add calculated load Upgrade Sizing: determine additional requirements and add calculated load

SAP 2009 4

Post-GoLive Sizings: General Procedure

Prerequisites
The system is live The hardware and software are scalable Different goals Re-Sizing: Only add volume, no modified processes Delta sizing: Add different functions Upgrade sizing: only upgrade SAP software

Procedure
1. Monitor CPU utilization, table growth, and memory use OS monitor ST06 Database monitor DB02 Front-end network load (statistical data records, ST03) Relate it to a meaningful business entity, such as the number of concurrent users or the number of active projects 2. Different procedures according to goals Re-sizing: Add the load coming in through the additional users and projects causing the same load structure Delta sizing: treat like a new sizing and add calculated load Upgrade sizing: determine additional requirements and add calculated load 3. Judge whether your current hardware is sufficient, or whether you may need to buy new hardware

SAP 2009 5

Re-Sizing: Overview

Situation
Plan to extend an existing application by volume and time periods only

Prerequisites
Your system is live The hardware and software are scalable Only add volume, no modified processes

Procedure
1. Monitor CPU utilization, table growth, and memory usage
OS monitor ST06

Database monitor DB02 Front-end network load (statistical data records, ST03) Relate it to a meaningful business entity, such as the number of concurrent users or the number of active projects

2. Add the load coming in through the additional users and projects causing the same load structure 3. Judge whether your current hardware is sufficient, or whether you may need to buy new one

SAP 2009 6

Example of a Re-Sizing

A company
Has 50 subsidiaries Template-based approach
Most subsidiaries will have a very similar customizing

Phased rollout
First, 5 subsidiaries go live Then the next 5-10 will follow suit, and so on

Consequence
Initial sizing for first go-live Possibly perform expert sizing on non-template-like subsidiaries Sizing verification of first go-live Re-sizing based on production system data (45 subsidiaries)

SAP 2009 7

Delta Sizing: Overview

Situation
Plan to add new functions to an existing system, for example, you decided to add supply chain management to your existing ERP solution

Prerequisites
Your system is live The hardware and software are scalable

Procedure
1. Monitor CPU utilization, table growth, and memory usage (as for re-sizing)

2. Obtain required additional load by applying appropriate sizing method such as Quick Sizer, expert sizing for sizing the new functions 3. Add the load coming in through the additional functions to the current requirements 4. Judge whether your current hardware is sufficient, or whether you may need to buy new one

SAP 2009 8

Example of a Delta Sizing

A company
Has 50 subsidiaries live with SAP ERP Wants to add SAP CRM functions

Phased rollout
First, 5 subsidiaries go live Then the next 5-10 will follow suit, and so on

Consequence
Initial sizing for first go-live For example, Quick Sizer, additional guidelines Possibly perform expert sizing on non-template-like subsidiaries Sizing verification of first go-live Re-sizing based on production system data (45 subsidiaries)

SAP 2009 9

Upgrade Sizing: Overview

Situation
Plan to upgrade to a new SAP release

Prerequisites
Your system is live, focus is only on SAP software The hardware and software are scalable

Procedure
1. Monitor CPU utilization, table growth, and memory usage (as for re-sizing) 2. Ideally, benchmark your key transactions in both releases
1.Identify bread-and-butter transactions 2.Benchmark them in production release A and in test release B 3.Apply obtained delta

3. If the ideal situation is not possible, use SAP notes that describe the influence of the upgrade on CPU, disk, memory, and front-end network in a hardware-independent format. 4. Add the load caused by the upgrade to the current requirements 5. Judge, whether your current hardware is sufficient, or whether you may need to buy new one
SAP 2009 10

Example of an Upgrade Sizing

A company
Has 50 subsidiaries live with SAP ERP 2005 Wants to upgrade to SAP ERP 6.0 Also wants to upgrade DB release

Consequence
Define scope of upgrade (SAP, DB, OS, HW) Analyze current utilization and growth Apply notes or benchmark transactions

SAP 2009 11

Procedure: How to Monitor Current Resource Utilization

Available monitors
Disk Analysis DB02, DB monitor of vendor (DB Performance Tables & Indexes) CPU Analysis ST06, ST03N, STAD, ST03G (Workload Analysis, Statistical Records, Global System Workload Analysis) User Analysis ST07, STAD, ST03G (Application Monitor, Statistical Records) Memory Analysis SM04, STAD, GCLOG (User List, Statistical Records) Front-End Network Load STAD, ST03N, ST03G, httplog (Statistical Records, Workload Analysis)

As a rule, 20% of the processes cause 80% of the load

Analyze Growth rate of 20 largest tables Average and peak CPU load Average and peak memory utilization

SAP 2009 12

Determining Disk Growth DB02 (1/2)

Check
Total available disk size Free space

SAP 2009 13

Determining Disk Growth (2/2)

Check
Monthly growth Drill-down to top 20 tables

SAP 2009 14

Determining CPU / Memory Utilization ST06

Check
Number of CPUs/cores CPU utilization Current and historic Detail Analysis Menu Available and free memory

SAP 2009 15

User Analysis (ST07)

For verification/Re-Sizing
Number of active users Think time can be modified

SAP 2009 16

Details on Re-Sizing

Examples of when re-sizing applies

The software needs to be physically moved to a different platform Multiple Components in One Database (MCOD) Merging different SAP systems Increasing The number of users Throughput

Note: It is important that the business functions will remain the same

Do not use the Quick Sizer for re-sizing

Goal of Quick Sizer Initial sizing based on SAP standard configurations and assumptions

SAP 2009 17

Details on Delta Sizing

Examples of when delta sizing applies

Adding another solution/application/function Modifying Business applications User mix

SAP 2009 18

Details on Upgrade Sizing

Distinguish the kind of upgrade

SAP software Database, operating system Hardware in general Configuration and parameter settings may change Very often, in an upgrade project, also business processes may be modified (delta sizing)

Upgrading may also involve

Re-design of configuration For example If wait times on some work processes are long before the upgrade, they will surely take even longer after the upgrade. In this case you must define additional work processes. The same applies to memory, additional memory requirements may require larger buffers See the service "GoingLivefor Functional Upgrade" from SAP's support organization

SAP 2009 19

Potential Issues in an Upgrade Sizing Project

At some stage in the project, these effects may need to be considered

Database server is used as application server Additional database users Indirect effects due to buffer sizes, longer transactions Different behavior of query optimizer Changes of the hardware and software configuration Some processes dominate resource consumption

SAP 2009 20

Straightforward Procedure

You have analyzed the current system resource consumption for

Disk space CPU consumption Memory consumption

In a first step, use the SAP standard notes, which are based on weekly regression measurements of top 100 transactions Example
Current monthly disk growth = 200 GB Note + 5%: 200 GB * 1.05 = 210 GB growth Current avg. CPU utilization = 54% DB, 48% App server Note + 5%: DB 54 * 1.05 = 56.7% App 48 * 1.05 = 50.4% App server Current memory used = 16.4 GB Note: +15% : 16.4 * 1.15 = 18.9 GB

SAP 2009 21

Upgrading Over Different Releases

In the standard case, simply apply several notes

Example ERP: SAP Notes 323263, 517085, 752532, 778774, 901070 You want to upgrade from release A to release C Procedure: Add the notes on resource requirements Base release A release B release C Example: The notes say A B +10% B C + 5% Calculate: Utilization_A * 1.1 * 1.05

1.80 1.70 1.60 1.50 1.40 1.30 1.20 1.10 1.00 4.6CSR1 47x110 47x200 ECC5.0 ECC6.0 4.6CSR1 47x110 47x200 ECC5.0 ECC6.0

utilization_A * 1.16

CPU/Memory Resource Consumption relative to 4.6C

CPU

Memory
upper range lower range

Note: Ranges do not constitute a maximum

Range: approx. 15-35%

SAP 2009 22

Range: approx. 40-70%

Upgrade and Unicode

Unicode requirements strongly depend on

The business process setup and configuration The platform for disk 30%-60% The processor type for CPU 10%-30%

Memory is hardware-independent: +50% Experience from migration projects

See service.sap.com/unicode-> Media Library -> Hardware Requirements

Recommended procedure: Perform own measurements

SAP 2009 23

Conclusion for Sizing on Production System Data

If you need to extend hardware
CPU extension of application servers can be done through Additional application servers Additional CPUs Faster CPUs Additionally, consider OS-dependent factors Pay attention to disk I/O

SAP 2009 24

Standard Post Go-Live Sizing Scenarios

+ Load Increase in % + Upgrade Increase in %

+ Quick Sizer Project + Load Increase in %

+ Quick Sizer Project + Upgrade Increase in %

Quick Sizer Project

Current Workload

Current Workload

Current Workload

Initial-Sizing

Upgrade or load increase

New functions or load increase

Upgrade & new functions

SAP 2009 25

Copyright 2009 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, SAP, SAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or noninfringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

SAP 2009 26