Principles of SAP HANA Sizing — - on premise and cloud

PUBLIC

Sebastian Schmitt, SAP

June, 2019

Principles of SAP HANA Sizing —on premise and cloud

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

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.


Sizing Introduction and Basics

Sizing Tools and Results

Sizing SAP HANA

Wrap-up

Agenda


SAP HANA Sizing KPIs – Game Changer

▪ Different sizing approach: SAP

HANA sizing vs. sizing of

traditional DB

▪ Memory is the leading driver for

SAP HANA sizing

▪ Massive parallelization in

analytical scenarios will have an

influence on Response Times;

hence CPU requirement will get

more important for analytical

scenarios

▪ Mixed transactional and

analytic workloads now

possible with SAP HANA but

compete for shared resources

▪ Disk is required for data persistence and for logging data

▪ Sufficient I/O performance required to enable processes to run with acceptable data throughput and storage system latency.

Disk size

Disk I/O

▪ Compared to anyDB, more CPU power is required to fully benefit from the parallel processing capabilities of SAP HANA for optimal response times

CPU

▪ Memory sizing is determined by the data footprint in SAP HANA (business and meta data in column and row store)

▪ Memory is also used by other components (e.g. SAP HANA caches) and for processing of requests

Memory

▪ Network sizing typically focuses on the bandwidth and is described in gigabits per second (gbps)

Front-end

Network Load


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 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.


Different Types of Sizing

Hardware Budget Sizing

Smaller companies

▪ Very simple algorithms

▪ Assumptions, likelihoods

▪ Level setting of project

▪ Risk identification

Advanced Sizing

Medium to large companies

▪ Throughput estimates

▪ Questionnaires, formulas

▪ Usage of standard tools

▪ Focus on core business processes

Re- / Delta / Upgrade Sizing

All projects

▪ SAP system monitors

▪ Goal: Extend an existing system by load / function

▪ Examples− Re-Sizing: Customer want to add 100 additional users who'll do the same

as the current productive ones

− Delta Sizing: Customer is live with CRM and want to add SCM

− Upgrade Sizing: Customer want to upgrade to latest EhP

Expert Sizing

Large or complex projects

▪ Additional guidelines

▪ Custom calculations

▪ Analysis of custom coding

▪ Custom sizing guidelines


Three-Party Collaboration Model

Contributions▪ Certified benchmarks →

scalable hardware

▪ Different configurations together with technology partners

▪ Service level agreements

▪ Final responsibility for sizing at customer site

Expectations from

benchmarking and sizing▪ Optimal performance

▪ Suggestion for HW config.

Contributions ▪ Response time

requirements

▪ Throughput requirements

▪ Provides business input

Contributions▪ Development and provision

of benchmark toolkits

▪ Regression testing for new releases

▪ Standard sizing guidelines

▪ Sizing verification processes

Hardware Vendors Customer

SAP

Sizing Recommendation

▪ CPU (SAPS)

▪ Memory (GB)

▪ Database space (GB)

▪ Disk I/O operations per sec

▪ Frontend bandwidth mbps

Sizing is the joint responsibility of

customer (LoB), SAP and HW Vendor.

But:

The main responsibility have the HW

Vendor. They have to make sure that

the SAP software runs smoothly at

customer site and that customers

don’t run into performance or TCO

issues due to under-sized or over-

sized HW.

Examples:

▪ Custom coding

▪ Different businesses require different sizings

▪ Different applications need different amounts of CPUs

▪ Additional needs might come from additional not sized usages


Risks in a Sizing Project

Challenge to obtain sufficient usage information as sizing input

Often caused by communication issues

Insufficient sizing input is compensated by assumptions, which should be documented

INCOMPLETE INPUT DATA

While it is perfectly ok to work with assumptions you must ensure that a verification process is included in the project plan

ASSUMPTIONS ARE NOT VERIFIED

Are very hard to predict: Make sure there is a verification process

Make sizing measurements, if required

CUSTOM CODING & SPECIAL DATA CONSTELLATIONS

Ris

ks in

a S

izin

g P

roje

ct




Sizing SAP HANA

Wrap-up

Agenda


Official SAP Sizing Page: www.sap.com/sizing

Guidelines

Access Sizing Guidelines

Access Sizing-related Materials

Tools

Access Quick Sizer *

Sizing Decision tree

Others

Training opportunities

FAQs

* Requires login credentials

http://www.sap.com/sizing


Initial Calculation Method

Educated guess

Questionnaire without formulas

For structured questions

T-Shirt Sizing

Simple algorithms with many assumptions

Formulas

Simple or more complex

Standard Sizing Methods and Tools

Quick Sizer

Supports user-

based and

throughput-based

sizing


Example: Quick Sizer, SAP’s Online Sizing Tool

▪ Structured sizing questionnaires

▪ Input for – Greenfield sizing– GoingLive Check

▪ Hardware vendor contact list

▪ Available online since 1996

▪ New Special Quick Sizer version for SAP S/4HANA Cloud

▪ HANA Quick Sizer version available since 09/2014

▪ Free of charge

▪ As of 2016: avg. 35,000 new projects per year

Characteristics

Facts and Figures

Scope

▪ SAP Key applications– SAP S/4HANA– HANA Standalone– SAP BW/4HANA– etc.

▪ Sizing by users and/or by throughput


4

3

2

1

Example: Greenfield Sizing with Quick Sizer

Check the list of certified AnyDB or HANA hardware to see which

hardware providers offer hardware configurations that match the sizing

result.

Provide the sizing result (or the Quick Sizer project number) to the

hardware vendor and get proposal for appropriate hardware

configuration and prices.

The Quick Sizer tool calculates the sizing result based on the input

Create a Quick Sizer project and provide input on the business

usage/requirements of the customer into the Quick Sizer project.

http://www.sap.com/benchmarks

https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/index.html




Sizing SAP HANA

Wrap-up

Agenda


SAP HANA Sizing - Overview

Customer Interested in

SAP HANA

Migrate existing

SAP applications

to SAP HANA (Migration Sizing)

New SAP HANA

system (Greenfield Sizing)

Sizing

Verification

Greenfield

A new SAP

application, which did

not exist before

Brownfield (system

conversion)

The SAP application

exists on anyDB,

anyOS, maybe in a

backlevel release

Sizing Verification

After the system runs on

SAP HANA, check

whether the capacity

estimation was right

Sizing Type

Definition


SAP HANA Sizing

Customer Interested

in SAP HANA

New SAP HANA system

(Greenfield Sizing)

Existing SAP system migrated to SAP HANA

(Migration Sizing)

Use SAP HANA Quick Sizer(www.sap.com/sizing)

Use Migration Reports/ Procedure(Notes: 1872170, 1793345, 2296290)

Find deployment options:

Connect with hardware vendor and check for

configuration

Certified and Supported SAP

HANA® Hardware Directory

Link:

http://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/index.html

Greenfield Sizing


Methodology and sizing result

• Structured questionnaires for key SAP applications

• Sizing results given in SAPS (CPU), GB (Memory and disk) and disk I/O

• Optional: Memory for persistent Memory (NVRAM)

Greenfield Sizing

New SAP HANA system

(Greenfield Sizing)

Use Quick Sizer• HANA version

• S/4HANA Cloud version

Sizing GuidelinesExpert Sizing for HANA

native

Services

• Request MAXAttention Service or

Sizing Service from Consulting

Sizing document

• Overview about architecture and functionalities for selected business scenarios

• Sizing results given as T-Shirt categories in SAPS (CPU) and GB (Memory & disk)

https://apps.support.sap.com/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sap/qs_oberflaeche/hana.do?bsp-language=en

https://apps.support.sap.com/sap/bc/bsp/sap/qs_oberflaeche/hana.do?sap-language=en&bsp-language=en

https://apps.support.sap.com/sap/bc/bsp/sap/qs_oberflaeche/cloud.do?sap-language=en&bsp-language=en

https://www.sap.com/about/benchmark/sizing.sizing-guidelines.html#sizing-guidelines


Greenfield Sizing for SAP S/4HANA

For greenfield sizing for SAP S/4HANA, use

HANA version of Quick Sizer on

www.sap.com/sizing

Please note:

The basics of the calculations are the same in HANA

QS and in the Classic QS, e.g., the think times of the

different user types (low, medium, high) are the same.

But: The sizing algorithms are different


http://www.sap.com/sizing


Demo

Quick Sizer

New Quick Sizer

Features


Data Aging

Data aging is a business data management concept for reducing the memory footprint in

SAP HANA

▪ Only operationally relevant (“hot”/current) data is loaded into main memory of SAP HANA

▪ Other (“cold”/historical) data remains primarily stored on disk, not affecting hot data performance, yet cold data

remains accessible via SQL on request


HANA Quick Sizer News Data Aging in HANA Quick Sizer

There are two residence periods. One for memory (aging period) and one for disk (archiving period).

▪ There are aging objects available, if the aging column (residence time in memory) is changeable. Per default

the aging period has been set to 24 months.

▪ There are no aging objects available, if the aging column (residence time in memory) is empty and highlighted

in blue.

▪ Introduction of ‘What if analysis for the retention times (disk/memory)’


Example What-If Analysis Data Aging

Option 1: HANA Memory Result – 4.2TB for S/4HANA Server (24-month residence time in memory)

Option 2: HANA Memory Result – 8.9TB for S/4HANA Server (no data aging)


SAP HANA requires adequate I/O performance to support processes such as:

▪ Savepoint writing

▪ Delta merges

▪ Database startup times

Storage systems running with SAP HANA must provide sufficient I/O performance to enable processes to run

with acceptable data throughput and storage system latency.

The calculation of the disk I/O requirements with the SAP HANA Quick Sizer is now possible.

HANA Quick Sizer News HANA Disk I/O


HANA Quick Sizer News 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


HANA Quick Sizer NewsSizing SAP S/4HANA Embedded Analytics

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

If the input of the involved sizing (e.g. Business area: Sales & Service) for embedded analytics is too big, no

sizing result will be calculated. The following message appears to execute at least one of the following actions:

1. Review and/or reduce the Concurrent Users sizing(s) of questionnaire 'X (e.g. Sales & Service)’

2. Delete sizing(s) on questionnaire 'SAP S/4HANA Embedded Analytics' for questionnaire 'X

3. If you consider your input numbers as appropriate then please contact SAP (CSS component: XX-SER-

SAPSMP-ST)


What is Persistent Memory: Persistent memory (non-volatile RAM, also referred to as Storage Class

Memory) is supported in SAP HANA as a persistent storage type.

Persistent memory (or NVRAM) is an emerging class of memory which combines the qualities of both DRAM

and Flash storage and bridges the gap between disk storage and main memory.

▪ Market launch depends on hardware roadmap

– HANA-servers with Intel Cascade Lake CPUs

Calculation:

Persistent Memory: Amount of memory required for the column store data

DRAM: Total HANA Memory – Persistent Memory

HANA Quick Sizer NewsPersistent Memory

How to Size SAP

S/4HANA Cloud?


Since June 2018, there is a new Quick Sizer for SAP S/4HANA

Cloud available

The tool can be used for S/4HANA Cloud greenfield sizings

Main Characteristics of the Cloud Quick Sizer

▪ Simplified UI

▪ Streamlined Input Navigation Tree (scope items)

▪ Documentation in the SAP Help Portal

▪ External usage: Only two sizing KPI’s (HANA RAM for Business data &

Frontend Network Load)

▪ Internal Usage: The two new KPIs (HANA RAM for Business data &

Frontend Network Load) + CPU, disk space & Disk I/O

▪ Sizing of API calls

Sizing SAP S/4HANA Cloud Quick Sizer

Migration Sizing


Migration Sizing Part 1/2

Existing NW ABAP system to be

migrated to SAP HANA

SAP Notes 1872170; 1793345

SAP S/4HANA SAP BW/4HANA

SAP Note 2296290

Back to Overview

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: Will be included in the sizing report (type ful in transaction

box). Recommendation: Double-check result with method as

described in SAP Note 1793345

Methodology and result

• 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 sizing will be available soon

https://launchpad.support.sap.com/#/notes/1872170/E


https://launchpad.support.sap.com/#/notes/2296290


Sizing Report for SAP S/4HANA

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

https://css.wdf.sap.corp/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?iv_language=E&param=69765F6D6F64653D3030312669765F7361706E6F7465735F6B65793D303132303033313436393030303030383035353732303133267361702D6C616E67756167653D452669765F6C616E67756167653D45


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.


How to Interpret the Results of the SAP S/4HANA Sizing Report

▪ Column store and row store estimations have good enough accuracy (10-20%). Still, do not forget it is an

estimation.

▪ Work Space (temporary memory) estimation uses a simple formula (data size in memory) * 2. Based on

experiences, if the work space is bigger than 3TB, it might be oversized.

▪ Always check the top tables. Very often, you will find basis tables with deletion/archiving potential such as

idoc, workflow, application log tables, etc. See SAP Note 706478 – “Preventing Basis tables from increasing

considerably” for more details.

▪ The total estimated memory requirement given by the report should not be considered as the final memory

sizing result. Take into account that:

– Not all the server physical memory will be available to HANA (OS and other processes are run too).

– There should be enough space left for future data growth or functional extension

▪ The sizing report takes a snapshot. Any growth between that date and the go-live date should be considered.


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!

Sizing Report for SAP BW/4HANA

Mission statement

Provide an easy to use, source database independent tool to predict resource requirements for a

BW system on a SAP HANA database.


Migration Sizing Part 2/2

Existing Non-NW-based system to be

migrated to SAP HANA

•Analysis of Legacy

system

•SAP HANA version

of Quick Sizer

SAP S/4HANAHANA native

•Analysis of Legacy

system

•SAP Note 1514966

•Request a sizing

service

Existing NW Java system to be migrated

to SAP HANA

Expert Sizing

Sizing Guidelines

Back to Overview

https://apps.support.sap.com/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sap/qs_oberflaeche/hana.do?bsp-language=en



mailto:[email protected]>

https://www.sap.com/documents/2016/10/822c3247-927c-0010-82c7-eda71af511fa.html

https://www.sap.com/about/benchmark/sizing.sizing-guidelines.html#sizing-guidelines

Sizing Verification


Sizing Verification

Existing SAP HANA System

Non-NW products

on SAP HANA

SAP Note

1872170

SAP Business

Suite powered by

HANA & SAP

S/4HANA

Industry

Solutions

powered by SAP

HANA

SAP NW BW

powered by

HANA &

BW/4HANA

SAP Note

2296290

Early Watch

Alert

SAP Note

1969700

SAP Note

1698281

Back to Overview

http://service.sap.com/sap/support/notes/1872170


http://service.sap.com/sap/support/notes/1736976


https://support.sap.com/content/dam/support/en_us/library/ssp/offerings-and-programs/support-services/sap-earlywatch-alert/warlywatch-alert-sap-one-support-portal.pdf



Deployment Options


Deployment Options

Virtualization – 1788665 - SAP HANA Support for virtualized / partitioned (multi-tenant) environments

Infrastructure as a Service (IaaS) – Certified and Supported SAP HANA Directory

Physical server – Certified and Supported SAP HANA Directory





Sizing SAP HANA

Wrap-up

Agenda


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 1698281 - Assess the memory consumption of a SAP HANA System

▪ SAP Note 1514966 – SAP HANA: Sizing SAP In-Memory Database

HANA Quick Sizer (for greenfield sizing)

Youtube Video

Sizing Information and ToolsSources of published sizing documentation

* Requires login credentials

https://youtu.be/9zWuNlwQGM4


Key Points to Take Home

▪ Sizing means translating business requirements into hardware requirements

▪ The success of the sizing exercise almost entirely depends on the quality of the data

▪ Sizing involves very different people and teams within an organization

▪ Expert sizing is recommended for custom development

▪ 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

Contact information:

Sebastian Schmitt

SAP SE

Product Management

[email protected]

Cell: +49 151 18874932

Thank you.

mailto:[email protected]

© 2019 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.

www.sap.com/contactsap

Follow us

https://www.sap.com/copyright

https://www.sap.com/registration/contact.html

https://www.linkedin.com/company/sap

https://www.youtube.com/user/SAP

https://twitter.com/sap

https://www.facebook.com/SAP

Principles of SAP HANA Sizing — - on premise and cloud

Documents

Transcript of Principles of SAP HANA Sizing — - on premise and cloud