ADM115 02 02 post golive by besube

VIEWS: 179 PAGES: 14

									Post Go-Live Sizings

Performance & Information Lifecycle Management
Different Times, Different Phases, Different
Goals of Sizing

Sizing takes place in different phases of a project

       Project                 Business                                       Final              Going Live &
     Preparation               Blueprint                                   Preparation             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

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

 SAP AG 2009, 2
Possible Definitions for Different Types of

 Hardware Budget Sizing                       Advanced Sizing                          Expert Sizing          Go

 Smaller companies                     Medium to large companies             Large or complex projects
   Very simple algorithms                Throughput estimates                   Additional guidelines
   Assumptions, likelihoods              Questionnaires, formulas               Custom calculations

     Level setting of project             Usage of standard tools               Analysis of custom coding
     Risk identification                  Focus on core business                Custom sizing guidelines

Initial Sizings

                  Re-Sizing                      Delta Sizing                       Upgrade Sizing
 All projects                          All projects                          All projects

     SAP system monitors                  SAP system monitors                   SAP system monitors
     Goal: Extend an existing             Goal: Extend an existing              SAP Notes
     system by load                       system by functions                   Goal: Upgrade SAP software
         E.g. by volume                       By different functions, e.g.
         100 additional users who'll          you are live with CRM and
         do the same as the current           want to add SCM
         productive ones

Production Sizings – whenever there is a change in throughput, sizing must be done
 SAP AG 2009, 3
Production Sizings: General Procedure

  Monitor CPU utilization, table growth, and memory use
         Relate it to a meaningful business entity, such as the number of concurrent users or the number of
         active projects
  Different procedures according to goals
         Re-sizing: Add the load coming in through the additional users and projects causing the same load
         Delta sizing: treat like a new sizing and add calculated load
         Upgrade sizing: determine additional requirements and add calculated load
  Judge whether your current hardware is sufficient, or whether you may need to buy new hardware

             Re-Sizing                             Delta Sizing                       Upgrade Sizing
 All projects                           All projects                           All projects
     SAP system monitors                    SAP system monitors                    SAP system monitors
     Goal: Extend an existing               Goal: Extend an existing               SAP Notes
     system by load                         system by functions                    Goal:
          E.g. by volume                        By different functions, e.g.       Upgrade SAP software
          100 additional users who'll           you are live with CRM and
          do the same as the current            want to add SCM
          productive ones

SAP AG 2009, 4
Procedure: How to Monitor Current Resource

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
     Growth rate of 20 largest tables
     Average and peak CPU load
     Average and peak memory utilization

SAP AG 2009, 5
Determining CPU / Memory Utilization – ST06

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

SAP AG 2009, 6
Determining Disk Growth – DB02 (1/2)

                                   Total available disk size
                                   Free space

SAP AG 2009, 7
Determining Disk Growth (2/2)

                                 Monthly growth
                                 Drill-down to top 20 tables

SAP AG 2009, 8
User Analysis (ST07)

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

SAP AG 2009, 9
Effects of Upgrading on Sizing

Distinguish the kind of upgrade                         Upgrading may also involve
  Migration to unicode – separate procedure               Re-design of configuration
  SAP software                                            For example
  Database, operating system                                   If wait times on some work processes are
  Hardware in general                                          long before the upgrade, they will surely take
                                                               even longer after the upgrade. In this case
  Configuration and parameter settings may
                                                               you must define additional work processes
                                                               The same applies to memory, additional
  Very often, in an upgrade project, also business
                                                               memory requirements may require larger
  processes may be modified (delta sizing)
                                                          See the service ”GoingLive for Functional
                                                          Upgrade” from SAP Support

These effects may need to be considered
   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

Recommended procedure: Perform own measurements
SAP AG 2009, 10
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                              utilization_A * 1.16
     1.80                        CPU/Memory Resource Consumption relative to 4.6C


     1.50                 CPU                                        Memory
                                                                                                          upper range
                                                                                                          lower range   Ranges do not

                                                                                                                        constitute a maximum

                4.6CSR1 47x110    47x200   ECC5.0   ECC6.0 4.6CSR1 47x110      47x200   ECC5.0   ECC6.0

                Range: approx. 15-35%                          Range: approx. 40-70%
SAP AG 2009, 11
Standard Post Go-Live Sizing Scenarios

                                    + Load         + Quick Sizer     + Quick Sizer
                                 Increase in %        Project           Project

                                   + Upgrade
                                                      + Load           + Upgrade
                                 Increase in %
                                                   Increase in %     Increase in %

                  Quick Sizer
                                    Current           Current           Current
                                   Workload          Workload          Workload

         Initial-Sizing         Upgrade or load   New functions or   Upgrade & new
                                increase          load increase      functions

SAP AG 2009, 12
Thank you!        Questions?

SAP AG 2009, 13
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
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,, 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
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 non-
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 AG 2009, 14

To top