Introduction into

Post Go-Live Sizings

Performance & Scalability, SAP
November, 2023

Public
Introduction

Details and Examples on Production Sizing (Brownfield Sizing)

Tools to Measure Resource Consumption

Sizing Verification

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
Public 3
Different Types of Sizing
Greenfield Sizing Brownfield Sizing Bluefield Sizing
Sizing of new applications from scratch Extension / migration of an SAP system Re-implementation of an
existing system
Hardware Budget Sizing Re-Sizing Selective Data
Smaller companies ▪ Tools: SAP system monitors Transition*
▪ Tools: Sizing Guidelines, Quick Sizer (user) ▪ Goal: Extend an existing system by load ▪ Tools: S/4HANA & BW/4HANA
▪ Very simple algorithms − e.g.,100 additional users who'll do the same as the current productive Sizing Reports
▪ Assumptions, likelihoods ▪ Re-Implementation with
Selective Transactional Data
Upgrade Sizing
Medium to large companies
▪ Tools: SAP system monitors
▪ Tools: Sizing Guidelines, Quick Sizer (throughput)
▪ SAP Notes
▪ Usage of standard tools
▪ Goal: Upgrade SAP software
▪ Focus on core business processes

Migration Sizing * Special case

▪ Tools: S/4HANA and BW/4HANA Sizing Reports Shell copy: Re-implementation
▪ Goal: Migrate ECC or BW system to S/4HANA or BW/4HANA without transactional data, but with
old customizing and master data

Delta Sizing
▪ Tools: ▪ Goal: Extend an existing system by new functions
− SAP system monitors − e.g., you are live with SAP S/4HANA and want to add SAP EWM or Not applicable
SAP S/4HANA embedded analytics
− Sizing Guidelines, Quick Sizer for additional load

Expert Sizing
▪ Additional guidelines ▪ Analysis of custom coding
Large or complex projects
▪ Custom calculations ▪ Custom sizing guidelines

Public 4
Finding the correct sizing approach
Greenfield, Bluefield (flavor of Brownfield) and (real) Brownfield Sizing

Customer needs to size systems

running on SAP S/4HANA / BW/4HANA

Existing SAP system fully Existing SAP system converted to SAP

Net new SAP S/4HANA application
converted to SAP S/4HANA / BW/4HANA S/4HANA via Selective Data Transition

Re-Implementation with Selective

New Implementation approach System Conversion approach
transactional Data
“Greenfield Sizing” "Brownfield Sizing" "Bluefield Sizing“ *

Use SAP HANA-based Quick Use Sizing Reports/ Procedure

Sizer / Sizing Guidelines (Notes: 1872170, 2296290)

Find deployment options: Certified and Supported SAP HANA®

Connect with hardware vendor and check for Hardware Directory
configuration Link:

* Special case - Shell copy: Re-implementation without transactional data, but with old customizing and master data
Public 5
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

Brownfield Sizing Delta Sizing (combination

Re-Sizing Upgrade Sizing brownfield/greenfield)
All projects All projects All projects
▪ SAP system monitors ▪ SAP system monitors ▪ SAP system monitors
▪ Goal: Extend an existing system by load ▪ SAP Notes ▪ Goal: Extend an existing system by functions
− e.g., by volume 100 additional users who'll do ▪ Goal: Upgrade SAP software (e.g. new sizing with Quick Sizer)
the same as the current productive ones − By different functions, e.g., you are live with CRM
and want to add SCM
Public 6
Introduction

Details and Examples on Production Sizing (Brownfield Sizing)

Tools to Measure Resource Consumption

Sizing Verification

Public 7
Production Sizings (Brownfield Sizing): 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 new functions
– Upgrade sizing: only upgrade SAP software

Procedure
▪ Monitor CPU utilization, table growth, and memory use
– Relate it to a meaningful business entity, e.g. 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. Delta sizing is a combination between
brownfield and greenfield sizing
– 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
Public 8
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
• Do not use the Quick Sizer for re-sizing. Goal of Quick Sizer: Initial sizing based on SAP standard
configurations and assumptions
Public 9
Example Upgrade Sizing

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

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

Note
• Very often, in an upgrade project, also business processes may be modified (delta sizing)
• Configuration and parameter settings may change. Re-design of configuration might be required

Public 10
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
Example SAP Note 1974405
▪ 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 + 10%:
– DB 54 * 1.1 = 59.4%
– App 48 * 1.1 = 52.8% App server
▪ Current memory used = 16.4 GB
– Note: +5%: 16.4 * 1.05 = 17.2 GB
Public 11
Upgrade Sizing
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 ECC6.0

• Base release A → release B → release C 1.70

Example: The SAP Notes say 1.60

1.50
CPU Memory
• A → B +10%
1.40

• B → C + 5% 1.30

Calculate: 1.20

1.10
• Utilization * 1.1 * 1.05 → utilization * 1.16
1.00
ECC6.0 EhP1 EhP2 EhP3 EhP4 ECC6.0 EhP1 EhP2 EhP3 EhP4

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

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

Public 12
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

Public 13
Introduction

Details and Examples on Production Sizing

Tools to Measure Resource Consumption

Sizing Verification

Public 14
Productive Sizing
How to Monitor Current Resource Utilization

Selection of available monitors

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

Public 15
Determining CPU / Memory Utilization – ST06

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

Public 16
Determining Disk Growth – DB02 (1/2)

Check
 Total available disk size
 Free space

Public 17
Determining Disk Growth (2/2)

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

Public 18
Introduction

Details and Examples on Production Sizing

Tools to Measure Resource Consumption

Sizing Verification

Public 19
SAP ONE Support Services

SAP EarlyWatch Alert (https://support.sap.com/ewa)

• SAP EarlyWatch Alert (EWA) is an important part of making sure your core business processes work
• Tool that monitors the essential administrative areas of SAP components and keeps you up to date on their performance
and stability
• SAP EWA collects detailed CPU and RAM usage statistics
• SAP EWA runs automatically to keep you informed, so you can react to issues proactively, before they become critical
• It gives an overview on solution-based KPIs and alerts and evaluates the performance of cross-component business
processes.

IT Planning Service
• SAP AGS IT Planning provides help for IT decision - making processes like review of concepts for solution landscapes or
operations strategies that fulfill the SAP customer’s long term requirements. They are scoped individually for each
situation.
• Services are delivered in different flavors: capacity management and technical architecture for MaxAttention customers,
and within SAP Value Assurance when planning for SAP S/4HANA and Analytics.

List of additional services can be found here

Public 20
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: Brownfield Sizing: Brownfield / Greenfield Brownfield / Greenfield

New SAP Application from Upgrade (Upgrade Sizing) Sizing: New functions Sizing: Upgrade (Upgrade
scratch or load increase (Re- (Greenfield: Quick Sizer) or Sizing) & new functions
Sizing) load increase (Re-Sizing) (Greenfield: Quick Sizer)
Public 21
Thank you.
Contact information:

Sebastian Schmitt
[email protected]

© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material.