Sizing

SAP HANA
Performance & Scalability, SAP
December, 2020

PUBLIC
Disclaimer

This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other
agreement with SAP. SAP has no obligation to pursue any course of business outlined in this
presentation or to develop or release any functionality mentioned in this presentation. This
presentation and SAP's strategy and possible future developments are subject to change and may
be changed by SAP at any time for any reason without notice. 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-infringement. SAP assumes no responsibility
for errors or omissions in this document, except if such damages were caused by SAP intentionally
or grossly negligent.

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

Agenda

Sizing introduction and basics

Sizing SAP HANA

▪ Greenfield
▪ Migration
▪ Deployment options

Wrap-up

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Performance requirements: Sizing
Sizing-relevant KPIs (Key Performance Indicators)

▪ From a customer perspective, sizing is the translation of business requirements (business throughput
and user concurrency requirements) into hardware requirements.

▪ From an SAP development standpoint, sizing refers to the creation of a sizing model for the product
functionality with a reasonable number of input parameters and assumptions. The goal is to define a
sizing guidance for each SAP application.

▪ The sizing procedure helps customers determine the resources (CPU, memory, data growth on disk, disk
I/O and frontend network) required by an application within the customer's business context. For on-
premise applications the sizing procedure is publicly available.

▪ Sizing is not configuration: Actual system configuration is a task performed by the hardware vendor or the
Infrastructure as a Service Provider who must ensure the system landscape meets the hardware
requirements determined by sizing.

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

SAP HANA Sizing KPIs

▪ Memory sizing is determined by the data footprint in SAP ▪ Different sizing approach: SAP
HANA (business and meta data in column and row store) HANA sizing vs. sizing of
Memory
▪ Memory is also used by other components (e.g. SAP HANA traditional DB
caches) and for processing of requests
▪ Memory is the leading driver for
SAP HANA sizing
▪ Compared to anyDB, more CPU power is required to fully
▪ Massive parallelization in
CPU benefit from the parallel processing capabilities of SAP
analytical scenarios will have an
HANA for optimal response times
influence on Response Times;
hence CPU requirement will get
▪ Disk is required for data persistence and for logging data more important for analytical
Disk size
▪ Sufficient I/O performance required to enable processes to run scenarios
Disk I/O with acceptable data throughput and storage system latency.
▪ Mixed transactional and
analytic workloads now
possible with SAP HANA but
Front-end ▪ Network sizing typically focuses on the bandwidth and is compete for shared resources
Network Load described in gigabits per second (gbps)

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

Memory: Leading Driver for SAP HANA Sizing

▪ The main driver for memory sizing is the table data of the planned SAP HANA system
▪ Most tables are located in the highly compressed column store of SAP HANA
▪ For working memory (or work space or temporary memory) of the database and temporary calculations,
almost the same size as for table data is required additionally
▪ A SAP HANA database includes further memory areas, such as code, stack, caches, operating system, and
other system files. These areas are typically small compared to a typical database.

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

Universally applicable statements on sizing

“
20% of the transactions and scenarios
create 80% of the load

Reliable sizing can only be done with

“ ▪ Scalable application software

▪ Scalable hardware
▪ Meaningful and nearly complete volume throughput or active
user information

“
Landscaping and configuration
are related, but are separate tasks

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Agenda

Sizing introduction and basics

Sizing SAP HANA

▪ Greenfield
▪ Migration
▪ Deployment options

Wrap-up

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

 SAP HANA Sizing - Overview

Customer Interested in
SAP HANA

Migrate existing
New SAP HANA
Sizing Type SAP applications Sizing
system
to SAP HANA Verification
(Greenfield Sizing)
(Migration Sizing)

Greenfield Brownfield (system Sizing Verification

Definition A new SAP conversion) After the system runs on
application, which did The SAP application SAP HANA, check
not exist before exists on anyDB, whether the capacity
anyOS, maybe in a estimation was right
backlevel release
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9
SAP HANA Sizing

Customer Interested
in SAP HANA

New SAP HANA system Existing SAP system migrated to SAP HANA
(Greenfield Sizing) (Migration Sizing)

Use SAP HANA Quick Sizer Use Migration Reports/ Procedure

(www.sap.com/sizing) (Notes: 1872170, 1793345, 2296290)

Certified and Supported SAP

Find deployment options: HANA® Hardware Directory
Connect with hardware vendor and check for
configuration Link:

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

Greenfield Sizing
Greenfield Sizing for SAP HANA

For greenfield sizing for SAP HANA,

use HANA version of Quick Sizer on
www.sap.com/sizing

Please note:
Not all applications are part of Quick
Sizer. Please also consult our sizing
guidelines.

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

Greenfield Sizing

New SAP HANA system

(Greenfield Sizing)

Use Quick Sizer

Expert Sizing for HANA
• HANA version Sizing Guidelines
• S/4HANA Cloud version
native

Methodology and sizing result

Sizing document Services
• Structured questionnaires for key
SAP applications • Overview about architecture and • Request MAXAttention Service or
• Sizing results given in SAPS (CPU), functionalities for selected business Sizing Service from Consulting
GB (Memory and disk) and disk I/O scenarios
• Optional: Memory for persistent • Sizing results given as T-Shirt
Memory (NVRAM) categories in SAPS (CPU) and GB
(Memory & disk)

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

Special Quick Sizer Features
Sizing SAP HANA
SAP HANA Quick Sizer: System Business Startup Time for Disk I/O Calculation

This input field 'System Business Startup time' shows the time until the database is usable for
business processes.

SAP HANA requires adequate I/O performance.

The system business startup time influences the calculation of the disk I/O requirements.

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

Sizing SAP HANA
SAP HANA Quick Sizer: Example for Different System Business Startup Times

Result for default business system startup time (30 minutes) – Data I/O category S

Result for shorter business system startup time (10 minutes) – Data I/O category M

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

Sizing SAP HANA
SAP HANA Quick Sizer: System Lifetime

System lifetime refers to the lifecycle of a system from deployment to retirement.

On the project and input questionnaires 'System lifetime' can be inserted, default value is 36 months.

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

Sizing SAP HANA
SAP HANA Quick Sizer: Example for Different System Lifetimes

Result for default system lifetime (36 months, growth rate 5 %)

Result for longer system lifetime (60 months, growth rate 5 %) – increased results for memory and
disk

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

Sizing SAP HANA
SAP HANA Quick Sizer: Sizing SAP Fiori Frontend Server

SAP Fiori Launchpad (FLP) Logon is the most influencing sizing factor

Determine Your FLP Logon Scenario for FES Sizing

▪ The total resource consumption has two parts, the one on the SAP Fiori Front-End Server, and the other one
on the SAP S/4HANA Back End
▪ For Fiori Front-End Server Sizing, please use the SAP Fiori Front-End Server Sizing” in the Quick Sizer and
estimate the maximal number of FLP logons per hour at peak time

Please Don’t Forget to Size the Back-End for Your Application Areas

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

Sizing SAP HANA
SAP HANA Quick Sizer: Sizing SAP S/4HANA Embedded Analytics

The goal of sizing for Sizing SAP S/4HANA Embedded Analytics is:
▪ To determine how many CPU cores/threads and memory are required for the processing of target
number of parallel queries (without index support)
▪ And at the same time achieving the average target response time
▪ With the HANA Quick Sizer, you can conduct a sizing for analytical apps now

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

Sizing SAP HANA
SAP S/4HANA Embedded Analytics sizing has been implemented in the SAP HANA Quick Sizer

Greenfield for new

small systems

Greenfield for new

large systems

Brownfield for new

small systems

Brownfield for new

large systems
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 21
Sizing SAP HANA
Sizing SAP S/4HANA Embedded Analytics - Greenfield

Quick Sizer will calculate a result, if the limit of 500

million table lines in the biggest table is not
exceeded!

If the limit of 500 million table lines is exceeded, you’ll get an error message:

In this case, you can conduct an SAP S/4HANA embedded analytics sizing with table 2. Quick Sizer is not
calculating with fix response times and parallelization degrees
SAP Note 2815376
Greenfield sizing for SAP
S/4HANA embedded analytics

You have the chance to define the query response times and the degree of parallelization by setting
assumptions.
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 22
Sizing SAP HANA
Sizing SAP S/4HANA Embedded Analytics - Brownfield

Quick Sizer will calculate a result, if the limit of 500

million table lines in the biggest table is not exceeded!

If the limit of 500 million table lines is exceeded, you’ll get an error message:

In this case, you can conduct an SAP S/4HANA embedded analytics sizing with table 2.

SAP Note 2813738

Brownfield sizing for SAP
S/4HANA embedded analytics
You have the chance
▪ to define the query response times, degree of parallelization and the memory per query by setting
assumptions.
▪ to conduct own measurements (expert sizing). By measuring the memory per query, response times and
calculating the parallelization degree, you can enter the measured values into table 2.
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 23
Steps for an expert sizing

Activity

1 Identify the most important queries/apps

1b
1b Identify, how they will be used, e.g. filter criteria, authorizations and how often they will be executed

Run these queries on representative test data (ideally on a recent copy of the production data)
2 • Quality of test data
• Quantity of test data
Measure resource consumption (CPU/Memory) and response times and calculate the degree of
3
parallelization

4 Perform a forecast calculation based on the expected usage of the queries/apps

Decide whether optimizations are necessary and if yes analyze and optimize expensive queries and
5
retest
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 24
Sizing SAP HANA
SAP HANA Quick Sizer: Persistent Memory

Persistent memory (non-volatile RAM, also referred to as Storage Class Memory) is supported in SAP HANA
as a persistent storage type.

Calculation:
NVRAM (Persistent DB memory) = Total SAP HANA memory (DB memory) - DRAM

SAP Note 2786237 -

Sizing SAP HANA with
Persistent Memory
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 25
SAP HANA Quick Sizer
SAP HANA Quick Sizer: S/4HANA Scale-out

If the memory result exceeds a certain threshold, Quick Sizer provides the option for the S/4HANA
server scale-out calculation (Minimum size to start these calculations is HANA DB > 8TB).

Example for memory balanced mapping of applications to hardware nodes:

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 26

How to use the HANA Cloud Quick Sizer version?
Sizing SAP HANA Cloud Quick Sizer

Since 2018, there is a new Quick Sizer for SAP HANA Cloud
available

The tool can be used for HANA Cloud greenfield sizings

Main Characteristics of the Cloud Quick Sizer

▪ Simplified UI
▪ Streamlined Input Navigation Tree (scope items)
▪ Documentation in the SAP Help Portal
▪ Only two sizing KPI’s (HANA RAM for Business data & Frontend
Network Load)
▪ Sizing of API calls

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 28

Brownfield Sizing
Migration Sizing
Migration Sizing Part 1/2
Existing NW ABAP system to be
migrated to SAP HANA

SAP S/4HANA SAP BW/4HANA

SAP Notes 1872170; 1793345 SAP Note 2296290

Methodology and result Methodology and result

• Sizing report (note 1872170) which runs on the „legacy“ (anyDB,
anyOS) ABAP system to determine the required HANA RAM and disk
on the new HANA-based solution
• Potential areas for housekeeping, cleanup and archiving
• Report /SDF/HDB_SIZING (Modification 77) contains enhancement
for persistent memory sizing
• CPU sizing: Recommendation is to use the method as described in
SAP Note 1793345
• Sizing report (note 229690) which runs on the source BW
ABAP system to determine the required HANA RAM and disk.
• Potential areas for housekeeping, cleanup and archiving
• In addition, a HANA CPU requirement assessment is included
• Persistent Memory configurations are taken into account

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 30

Sizing Report for SAP S/4HANA (SAP Note 1872170)

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

Scope
▪ Runs on SAP_BASIS 620 and higher
▪ Is suitable for sizing of all Business Suite products (ERP, CRM, SCM, SRM, etc.)
▪ Not suitable for BW (Refer to SAP Note 2296290 – New Sizing Report for SAP BW/4HANA)

Functionality
▪ Considers SAP S/4HANA data model changes in FI, SD, MM, ML, etc.
▪ Estimates the maximum memory consumption of the database, if migrated to SAP HANA
▪ Is independent of the source database provider
▪ Considers distribution of tables to row and column store
▪ Considers differences for secondary indexes
▪ Considers compression of legacy database
▪ Considers data aging for technical objects
© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 31
Results of Sizing Report /SDF/HDB_SIZING

The sizing report includes the sizing projections, based on the actual table sizes in the legacy system as well
as an estimation of how much the memory footprint can be reduced using functionalities that HANA will
enable.

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 32

Sizing Report for SAP BW/4HANA (SAP Note 229690)

Mission statement
Provide an easy to use, source database independent tool to predict resource requirements for a
BW system on a SAP HANA database.

The sizing report /SDF/HANA_BW_SIZING is a convenient method to estimate the memory requirements
of a BW system after migration to SAP HANA. Major advantages of the ABAP report:
▪ Easy to deploy and use – no DB administrator required
▪ Independent of source database specific compression and data representation
▪ Considers user defined future growth and leverages BW semantic information

The report requires ST-PI 2008_1_7xx SP12 or ST-PI 740 SP1 and SAP NetWeaver BW 7.0 SP 4 or higher.
Updated versions can be obtained from SAP Note 2296290.
Important note for DB2 on iSeries (AS/400): Please implement SAP Note 1677958!

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 33

SAP HANA CPU Requirements Assessment

▪ Introduced with version 2.5 of sizing report/Tailored Datacenter Integration (TDI) Phase 5
▪ This is not a CPU sizing!
▪ Configuration space for SAP HANA hardware opened up to allow for more flexibility in combining memory
and CPU resources by introducing CPU Requirements classes
▪ SAP BW/4HANA sizing report enhanced by analysis process looking at historical OLAP statistics
▪ Customers running this analysis need to comply with side conditions listed in SAP note 2502280 and
confirm this explicitly on the selection screen:

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 34

SAP HANA CPU Requirements Assessment: Results

Recommended CPU power now part of

sizing results (only if compliance was
confirmed)

Results can be any of:

▪ CLASS L (100% CPU Req.):

SAPS close to the CPU power of a machine with standard configuration

▪ CLASS M (50% CPU Req.):

Half of SAPS for CLASS L

▪ CLASS S (25% CPU Req.):

Half of SAPS for CLASS M

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 35

Sizing Verification
Sizing Verification

Existing SAP HANA System

SAP Business Industry SAP NW BW

Suite powered by Solutions powered by Non-NW products
HANA & SAP powered by SAP HANA & on SAP HANA
S/4HANA HANA BW/4HANA

SAP Note
SAP Note Early Watch SAP Note 1969700
1872170 Alert 2296290 SAP Note
1698281

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 37

Deployment Options
Deployment Options

• Infrastructure as a Service (IaaS) – 1380654 - SAP support in IaaS

environments

• Virtualization – 1788665 - SAP HANA Support for virtualized / partitioned (multi-

tenant) environments

• Physical server – Certified and supported SAP HANA directory

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 39

Agenda

Sizing introduction and basics

Sizing SAP HANA

▪ Greenfield
▪ Migration
▪ Deployment options

Wrap-up

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 40

Key Points to Take Home

▪ Sizing means translating business requirements into hardware requirements

▪ The HANA sizing approach is different from the sizing of traditional databases
▪ Sizing is not configuration
▪ Greenfield sizings for HANA should be done with the HANA Quick Sizer and
migration sizing of an existing NetWeaver-based system to SAP HANA should be
done with the corresponding migration reports

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 41

Additional Resources
Sizing information and tools - Sources of published sizing documentation

www.sap.com/sizing
▪ Access to Quick Sizer
▪ Access to sizing guidelines, for example, SAP HANA accelerators

SAP Support Portal

▪ SAP Note 1872170 – SAP S/4HANA memory sizing
▪ SAP Note 1793345 – Sizing for Suite on HANA
▪ SAP Note 2296290 - New Sizing Report for BW/4HANA
▪ SAP Note 1969700 - SQL Statement Collection for SAP HANA
▪ SAP Note 1698281 - Assess the memory consumption of a SAP HANA System
▪ SAP Note 1514966 – SAP HANA: Sizing SAP In-Memory Database
▪ SAP Note 2779240 - Workload-based sizing for virtualized environments
▪ SAP Note 2815376 - Greenfield sizing for SAP S/4HANA embedded analytics
▪ SAP Note 2813738 - Brownfield sizing for SAP S/4HANA embedded analytics
▪ SAP Note 1380654 - SAP support in IaaS environments
▪ SAP Note 2786237 - Sizing SAP HANA with Persistent Memory

SAP HANA Quick Sizer (for greenfield sizing)

YouTube Video

© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 42

Thank you.
Contact information:
Sebastian Schmitt
SAP SE
Product Management
sebastian.schmitt@sap.com
Cell: +49 151 18874932
Follow us

www.sap.com/contactsap

© 2020 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.