Sizing Saps

Sizing SAP S/4HANA using the Quick Sizer Tool
Sebastian Schmitt, SAP

June, 2017
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.
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Agenda
Sizing Introduction and Basics
Sizing Tools and Results
Sizing SAP S/4HANA
Wrap-up

SAP HANA Sizing KPIs – Game Changer
 Memory sizing is determined by the data footprint in SAP

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

Approaches to SAP HANA Sizing
General Information: Different Memory Areas in SAP HANA
Sizes Relevant memory parts

Room 1. The memory area allocated for
Pool
to grow table data, either row store or
column store.
2. Subsequently, the buffer for
Temporary memory Equal to table footprint dynamic and temporary
(assumed) computations is assumed to be
equal to the table data size
Results 3. “Offset” refers to space required
of sizing for code and stack, caches and
reports HANA Table data services and the operating system.
Table footprint
(row store and column store) (measured) Note: Used memory consists of
temporary memory parts and
table data, either in row store or
HANA caches and services (code and ~50 GB in column store. HANA code and
Sizing
stack included)
“offset” stack is also included, but usually
Depends on node size
Operating System negligible.

What are SAPS?
SAP Application Performance Standard (SAPS) is a hardware-independent measurement unit that

describes the throughput of hardware in an SAP environment.
Laptop
 1 processor Definition of SAPS:
 Quad-core
 Approx. 10,000 SAPS  Derived from Sales & Distribution (SD) Standard Application
Benchmark
Commodity server
 2 processors
 40 cores  100 SAPS = 2,000 fully-processed order line items per hour
 Approx. 90,000 SAPS
High-end server
 16 processors For more information on SAPS, see www.sap.com/benchmark
 244 cores → Measuring in SAPS
 Approx. 500,000 SAPS

Three-Party Collaboration Model
Sizing is the joint responsibility of

Hardware Vendors Customer customer (LoB), SAP and HW Vendor.
Contributions Expectations from
 Certified benchmarks  benchmarking & sizing
But:
scalable hardware Sizing Recommendation The main responsibility have the HW
 Optimal performance
 CPU (SAPS)
 Different configurations
 Memory (GB)
 Suggestion for HW config. Vendor. They have to make sure that
together with technology
partners  Database space (GB) Contributions the SAP software runs smoothly at
 Service level agreements  Disk I/O operations per sec  Response time customer site and that customers
 Final responsibility for sizing  Frontend bandwidth mbps requirements
at customer site  Throughput requirements
don’t run into performance or TCO
 Provides business input issues due to under or over-sized HW
SAP Examples:
Contributions  Custom coding
 Development and provision  Different businesses require
of benchmark toolkits different sizings
 Regression testing for new
releases  Different applications need different
 Standard sizing guidelines amounts of CPUs
 Sizing verification processes  Additional needs might come from
additional not sized usages
Agenda
Sizing SAP S/4HANA
Wrap-up

General Available 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

Standard Sizing Methods and Tools
Initial Calculation Questionnaire

Method without formulas
Educated guess For structured
questions
T-Shirt Sizing
Simple algorithms
with many
assumptions Quick Sizer
Supports user-
based and
throughput-based
Formulas sizing
Simple or more
complex

Example: Quick Sizer, SAP’s Online Sizing Tool
Characteristics
 Structured sizing questionnaires
 Input for
– Greenfield sizing
– GoingLive Check
 Hardware vendor contact list
Facts & Figures

 Available online since 1996
 New Special Quick Sizer version for SAP HANA available (since 09/2014)
 Free of charge
 As of 2016: avg. 35,000 new projects per year
Scope
 SAP Key applications
– SAP S/4HANA
– SAP Business Suite and Industries
– SAP NetWeaver®
– etc.
 Sizing by users and/or by throughput
Agenda
Sizing SAP S/4HANA
Wrap-up

SAP HANA Sizing – In a Nutshell
Customer Interested in
SAP S/4HANA
Existing SAP system

New SAP HANA system
(Greenfield Sizing)
migrated to HANA
(Migration Sizing)
Use HANA Quick Use Migration

Sizer Reports
Find deployment options:

Appliances, SAP Tailored Datacenter
Integration (TDI), Cloud via SAP Cloud
Appliance Library (CAL)
Connect with hardware vendor and

check for sample configuration or get
started with SAP CAL

Greenfield Sizing
Greenfield Sizing for SAP S/4HANA
For greenfield sizing for SAP S/4HANA, use HANA

version of Quick Sizer
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
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
Since February 2016, a data aging logic has been implemented in 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.
 Since March 2017: Introduction of ‘What if analysis for the retention times (disk/memory)’

Example What-If Analysis Data Aging
Option 1: HANA Memory Result – 4,2 TB for S/4HANA Server (24 month residence time in memory)
Option 2: HANA Memory Result – 8,9 TB for S/4HANA Server (no data aging)

Quick Sizer News
Sizing Principles for SAP Fiori Frontend Server (FES)
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 Frontend Server, and the other
one on the SAP S/4HANA Backend
 For Fiori Frontend Server Sizing, please use the SAP Fiori Frontend 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 Backend for Your Application Areas
Quick Sizer News
HANA Disk I/O
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.

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
 And at the same time achieving the average target response time.
Get the latest version of the Sizing Excel Questionnaire:

Example Analytical Fiori Applications
Please note:
HANA is designed for OLTP+OLAP. OLTP workloads can be sized with the Quick Sizer, whereas Analytical
Fiori Applications (OLAP) have to be sized additionally.

Example Analytical Fiori Applications
Input Be Careful:
 The SAPS out of the analytics sizing are very “peaky
SAPS”, which are needed to get the best possible
response times
 Customers have to be asked, whether this load may be
shifted to low load phases
 Customers have to decide, whether this optimal
Result response times justify systems, which have X times more
CPU power compared to what is needed just for the usual
throughput out of the usual sizing.
 Customers and hardware partners have to find a balance
between optimal response time on the one side and
minimized costs for hardware on the other side (also
higher response times might be acceptable for the
business of the customer)

Migration Sizing
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 1736976 – Sizing Report for SAP Business Warehouse on HANA)
Functionality
 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

SAP Simple Finance Sizing for Migration Sizings
The current version of the report is also valid for sizing of HANA 2.0. The report can also be used for
different sizing scenario such as SAP Suite on HANA, SAP S/4HANA Finance, SAP S/4HANA.
1872170 – Suite on HANA sizing report

Algorithm of Sizing Report /SDF/HDB_SIZING
• The total number of entries of each tables is read Example: A typical column
1 from the database statistics “mandt” has type c and values
such as ‘100’, ‘000’, ‘066’. The
report will calculate an average
size of 6 bytes for this column.
• A random sample of data is read from every
2 tables in the system
Example: Column “mandt” has an

• Out of this sample, the report calculates the average size of 6 bytes and the
average number of bytes per column tables has 100 records. Total
3 uncompressed size of the column
is 600 bytes.
• Out of the average size per column and the total
record count, the uncompressed size
4 of a column is calculated The size estimation for keys
(primary, secondary keys, etc.) is
• To the uncompressed size an average more complex (and more
compression factor is applied to get the accurate) but uses the same
5 estimated size in HANA. metrics (avg. size per column and
record count)

Results of Sizing Report /SDF/HDB_SIZING
The sizing report for SAP ERP on SAP HANA 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 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.

Memory Sizing Report News
(1872170 – Business Suite on HANA and S/4HANA sizing report)
Data aging estimation for Workflow document

 Added to already existing data aging estimation for Application log, Change documents and iDocs. The
addition of this objects completes the full coverage of “service objects”.
Sizing of upgrade shadow instances
Integration in S/4HANA readiness check

Memory Sizing Report News
Outlook
 Improve sizing of the “Work Space” (or temporary memory)
 Add more data aging objects to the report (especially, estimation of saving on “application objects”)
Other planned enhancements

 Integrate IOPS Sizing
 Reflect further simplifications in data model

Deployment Options
Active-Active Read Enabled
Load balance read-intensive operations

between a primary and secondary
instance of SAP HANA with the active /
active-read enabled mode.
 Currently „out of the box“ about 60
Apps are Active-active read enabled.
 Customer build queries
– Usage of generic analytical clients that use
analytical CDS views
– Own Smart Business Apps (and respective
adjustment of the Tile configuration)
– Own purely reading Apps (and respective
adjustment of the App Descriptor)
 Sizing: Beware that in case of a fail
over the complete load is on one
instance
 For resource intensive operations
available resources are used
SAP HANA Multitenant Database Containers (MDC)
 Multitenant Database Containers provide strong isolation capabilities

– Each tenant database has its own database admin and end users, database catalog,
repository, persistence, backups, traces and logs Application Application
– Tenants Memory and CPU consumption can be configured independently
– Integration with SAP HANA data center operation procedures, housekeeping, backups
(full and/or on tenant level), etc.
SAP HANA
 Multitenant Database Containers share one SID and Revision System
– Shared installation of database system software and therefore better usage of

hardware System DB
– Tenant databases are identified by name or port
– SAP HANA system replication covers whole system (Sys. DB and tenants)
– Additive sizing for all tenant database
Tenant Tenant
 Targeting MCOS-like on premise and SAP Cloud Platform scenarios DB DB
with a reasonable number of tenant databases per system.
Newest Adaptions in Quick Sizer and its Sizing / Configuration Impact
Impact on CPU requirements by applying the C2M ratio:

The ratio between CPU and The calculation of CPU requirements based on the memory footprint doesn’t
HANA Quick Sizer
calculates CPU and
memory differs significantly take these differences into account
memory independently amongst the available sizing  Risk of CPU over-sizing
elements  Risk of CPU under-sizing with wrongly perceived C2M*
(e.g. systems with high DB load)

Introduction of Data Data Aging can reduce the Reduced memory footprint will also lead to reduced CPU requirements.
Aging in Quick Sizer memory footprint significantly But: Data aging should not reduce the required CPU resources for OLTP load
 Increased risk of CPU under-sizing with wrongly perceived C2M*

To get the best possible
Introduction of sizing The calculation of CPU requirement based on the memory footprint might not
response times, the CPU
for Analytical reflect correctly the additional CPU requirements for OLAP workloads.
requirements can increase
Applications  Increased risk of CPU under-sizing with wrongly perceived C2M*
significantly
* Please note that the CPU requirements based on the C2M ratio are minimum CPU values. This is
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC often misunderstood by customers 37
Distribution: User-based Sizing Elements vs. C2M Ratio
Expected shifts
through Sizing of
Analytical Apps
Quick Sizer projects

Expected shifts with higher CPU
through Data results as projected
Aging effects by the C2M ratio

Deployment Options
Virtualization – SAP Note 1788665
Infrastructure as a Service (IaaS) – Certified and Supported SAP HANA Directory
Physical server – Certified and Supported SAP HANA Directory

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 1736976 – Sizing Report for BW on HANA
– SAP Note 1514966 – SAP HANA 1.0: Sizing SAP In-Memory Database
HANA Sizing – General

Introduction to Sizing on SAP HANA video
HANA Quick Sizer (for greenfield sizing) & SAP SoH Migration Sizing
Greenfield Sizing with SAP Quick Sizer demo video
* Requires login credentials

7 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
 Initial Sizing for HANA should be done with Quick Sizer
 Migration sizing of an existing system to SAP S/4HANA should be done following SAP Note
1872170

Thank you.
Contact information:
Sebastian Schmitt
Product Management
Performance & Scalability
SAP SE
Email: sebastian.schmitt@sap.com

Sizing Saps

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Sizing Saps

Transféré par

Droits d'auteur :

Formats disponibles

Sizing SAP S/4HANA using the Quick Sizer Tool

Sebastian Schmitt, SAP

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

Sizing Introduction and Basics

Sizing Tools and Results

Sizing SAP S/4HANA

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

 Memory sizing is determined by the data footprint in SAP

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

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

Sizes Relevant memory parts

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

SAP Application Performance Standard (SAPS) is a hardware-independent measurement unit that

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

Sizing is the joint responsibility of

Sizing Introduction and Basics

Sizing Tools and Results

Sizing SAP S/4HANA

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

* Requires login credentials

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

Initial Calculation Questionnaire

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

Facts & Figures

Sizing Introduction and Basics

Sizing Tools and Results

Sizing SAP S/4HANA

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

Existing SAP system

Use HANA Quick Use Migration

Find deployment options:

Connect with hardware vendor and

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

For greenfield sizing for SAP S/4HANA, use HANA

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

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

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

Determine Your FLP Logon Scenario for FES Sizing

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

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

Get the latest version of the Sizing Excel Questionnaire:

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

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

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

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

1872170 – Suite on HANA sizing report

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

Example: Column “mandt” has an

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

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

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

Data aging estimation for Workflow document

Sizing of upgrade shadow instances

Integration in S/4HANA readiness check

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

Other planned enhancements

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

Load balance read-intensive operations

 Multitenant Database Containers provide strong isolation capabilities

– Shared installation of database system software and therefore better usage of

Impact on CPU requirements by applying the C2M ratio:

Impact on CPU requirements by applying the C2M ratio:

Impact on CPU requirements by applying the C2M ratio:

Quick Sizer projects