Introduction into

Post Go-Live Sizings

SAP SE
2018

PUBLIC
Introduction

Details and Examples on Production Sizing

Tools to Measure Resource Consumption

Sizing Verification

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Sizing Goals in different phases of a customer project
Go
Live
Project Business Realization 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 Functional Business

Changes Units

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
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Different Types of Sizing

Greenfield Sizing Go
Live

Hardware Budget Sizing Advanced Sizing Expert Sizing

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 processes ▪ Custom sizing guidelines

Production Sizing
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 system by ▪ Goal: Extend an existing system ▪ SAP Notes
load by functions ▪ Goal: Upgrade SAP software
 e.g., by volume 100 additional users  By different functions, e.g., you are
who'll do the same as the current live with CRM and want to add SCM
productive ones

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Introduction – Sizing Approaches on Productive Data

Assumptions
▪ The system is properly tuned for optimal performance
▪ The focus is on net consumption of business processes on the hardware

Note: Resource consumption strongly depends on

▪ Business process: customizing, customer extensions
▪ Combination of hardware and software: configurations
▪ Recommendations refer to used resources, not allocated ones

Production Sizing
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 system by load ▪ Goal: Extend an existing system by functions ▪ SAP Notes
 e.g., by volume 100 additional users who'll do  By different functions, e.g., you are live with CRM ▪ Goal: Upgrade SAP software
the same as the current productive ones and want to add SCM

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Introduction

Details and Examples on Production Sizing

Tools to Measure Resource Consumption

Sizing Verification

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Production 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
▪ 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 structure
– 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
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
Example 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)

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

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Example 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)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

Example Upgrade Sizing

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

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

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

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 "GoingLive for Functional Upgrade" from SAP's support organization

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

Straightforward Procedure for Upgrade Sizing

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

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

Upgrading Over Different Releases

In the standard case, simply apply several SAP Notes

Example SAP ERP: SAP Notes 323263, 517085, 752532, 778774, 901070
To upgrade from release A to release C
▪ Procedure: Add the notes on resource requirements 1.80
CPU/Memory Resource Consumption relative to 4.6C

▪ Base release A  release B  release C 1.70

1.60
Example: The SAP Notes say CPU Memory
1.50

▪ A  B +10% 1.40

▪ B  C + 5% 1.30

1.20
Calculate:
1.10
▪ Utilization * 1.1 * 1.05  utilization * 1.16 1.00
4.6CSR1 47x110 47x200 ECC5.0 ECC6.0 4.6CSR1 47x110 47x200 ECC5.0 ECC6.0

Range: approx. 15-35% Range: approx. 40-70%

Note: Ranges do
not constitute a upper range
maximum lower range

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13

Conclusion for Sizing on Production System Data

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

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

Introduction

Details and Examples on Production Sizing

Tools to Measure Resource Consumption

Sizing Verification

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

How to Monitor Current Resource Utilization

Available monitors
▪ Disk Analysis DB02, DB monitor of hardware vendor
– (DB Performance Tables & Indexes)
▪ CPU Analysis ST06, ST03N, STAD, ST03G
– (Workload Analysis, Statistical Records, Global System Workload Analysis)
▪ User Analysis STAD, ST03G
– (Application Monitor, Statistical Records)
▪ Memory Analysis SM04, STAD
– (User List, Statistical Records)
▪ Front-End Network Load STAD, ST03N, ST03G
– (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

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16

Determining CPU / Memory Utilization – ST06

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

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17

Determining Disk Growth – DB02 (1/2)

Check
 Total available disk size
 Free space

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 18

Determining Disk Growth (2/2)

Check
 Monthly growth
 Drill-down to top 20 tables

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19

Determine HANA Memory and Disk (SAP Note 1872170) Requirements

Report /SDF/HDB_SIZING
▪ Described in SAP Note 1872170 – Suite on HANA sizing report

Scope
▪ Runs on SAP NetWeaver systems based on SAP HANA
▪ Not suitable for BW (Refer to SAP Note 2296290 - New Sizing Report for BW/4HANA)

Functionality
▪ Estimates the maximum memory and disk consumption of the database
▪ Additional functionality needs to be sized with the HANA Quick Sizer (Delta Sizing)

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 20

Introduction

Details and Examples on Production Sizing

Tools to Measure Resource Consumption

Sizing Verification

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 21

New set of SAP EarlyWatch® Alert Applications in the cloud

SAP EarlyWatch Alert Workspace:

The central landing page which gives

a comprehensive overview on your
system landscape regarding stability,
configuration, hardware utilization and
performance

Drill-downs into KPI time series for a

long time range are provided, e.g.
database growth, SAP HANA CPU
and memory utilization and response
launchpad.support.sap.com times.

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Focus is on-premise and private cloud systems 22
SAP EarlyWatch Alert - Cloud Applications
Landscape Overview Task list per customer Dashboard per System

• Identify largest systems • Solve alerts in whole landscape • Identify bottlenecks

• Find top alerts • Get automatic recommendations • Find critical trends in KPIs
• SAP Fiori Overview Page • Powered by HANA Text Search • Embedded analytics via CDS views
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 23
Integration into Solution Manager on-premise

Independent on SolMan release in EWA report:

SolMan 7.2 SP07 :

© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 24

Standard Scenarios for Production Sizings – a Mixture of Different
Approaches

+ Load + Quick Sizer + Quick Sizer

Increase in % Project Project

+ Upgrade + Load + Upgrade

Increase in % Increase in % Increase in %

Quick Sizer
Current Current Current
Project
Workload Workload Workload

Greenfield Sizing Upgrade or load New functions or Upgrade & new

increase load increase functions
© 2018 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 25
Thank You!

Sebastian Schmitt

[email protected]

© 2017 SAP SE or an SAP affiliate company. All rights reserved.