CAA303 Presentation

Sizing for
SAP S/4HANA and SAP S/4HANA Cloud

CAA303
PUBLIC
Speakers
Las Vegas
September 24–27, 2019
Detlef Thoms
Barcelona
October 8-10, 2019
Sebastian Schmitt
Bangalore
November 13-15, 2019
Sukshatha Rao
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Take the session survey.
We want to hear from you!
Complete the session evaluation for this session

CAA303 on the SAP TechEd mobile app.
Download the app from

iPhone App Store or Google Play.

Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation 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. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
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, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.

Agenda
Sizing introduction and basics
Sizing tools
Demo Quick Sizer
Sizing SAP S/4HANA and SAP S/4HANA

Cloud
 Greenfield
 Migration
 Deployment options

Agenda
Sizing tools
Demo Quick Sizer
Sizing SAP S/4HANA and SAP S/4HANA Cloud

 Greenfield
 Migration

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 a 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
who must ensure the system landscape meets the hardware requirements determined by sizing.

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

Ensuring scalability with performance tests – Approaches
Single user – Quality and implications of accesses to

test persistence layer
– Linear resource consumption
– Small test system
– (QA, development), one user Analyze & measure – Parallel processing mechanisms, load
scalable behavior balancing
– Memory usage and memory leaks
– Disk requirements
– Front-end network load
Performance predictions
Multi user test for high volume environment
(Volume)
– Equivalent to multi-user test, stress test,

load test, benchmark
Verify assumptions

SAP HANA sizing KPIs
 Memory sizing depends on the data footprint in SAP HANA  Different sizing approach: SAP
(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)

Different types of sizing
Hardware budget sizing Advanced sizing

Smaller companies Medium to large companies
 Very simple algorithms  Throughput estimates
 Assumptions, likelihoods  Questionnaires, formulas
 Level setting of project  Usage of standard tools and
 Risk identification guidelines
 Focus on core business
processes
Expert sizing
Re- / Delta / Upgrade / Migration sizing
Large or complex projects
All projects
 Additional guidelines
 SAP system monitors and statistics
 Custom calculations
 Goal: Extend an existing system by load / function
 Analysis of custom
 Examples coding
− Re-Sizing: Customer wants to add 100 additional users who'll do the same  Custom sizing guidelines
as the current productive ones
− Delta Sizing: Customer is live with SAP S/4HANA and wants to add EWM
− Upgrade Sizing: Customer plans to upgrade to latest EhP
− Migration Sizing: Customer want to migrate from ECC to SAP S/4HANA

Three-party collaboration model
Sizing is the joint responsibility of

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

Common factors that influence sizing
LEGEND: Responsibility of: Technology Partner | SAP | Customer
Customer Coding,
HW Platform System Settings Customizing 3rd Party
 Processor  Parameterization  Business process design  Performance impact
technology  Interfaces  Set up of business  Scalability
 Disk technology  Security settings processes  Business process design
 Network technology  Unicode  Organizational structures
 System infrastructure
SAP Software Document Volume Business & Data Growth User Behavior
 Release  Time for volume  Avoiding data  Concurrency
 OLTP or OLAP processing  Archiving strategies  LAN/WAN
 Industry solutions  Background processing,  Information Lifecycle  Internet/intranet
parallel jobs Management  Activity, e.g.
 Reporting  New functionality − *-Search
 Load from external  Mergers and acquisitions
− Efficient navigation
systems  Reporting
Customer Profile
Risks in a sizing project
 Challenge to obtain sufficient usage information as sizing

input
INCOMPLETE INPUT
 Often caused by communication issues
DATA
Risks in a Sizing Project
 Insufficient sizing input is compensated by assumptions,

which should be documented
 While it is perfectly ok to work with assumptions you must

ASSUMPTIONS ARE
ensure that a verification process is included in the project
NOT VERIFIED plan
CUSTOM CODING &  Are very hard to predict: Make sure there is a verification
SPECIAL DATA process
CONSTELLATIONS  Make sizing measurements, if required

Agenda
Sizing tools
Demo Quick Sizer

 Greenfield
 Migration

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

Standard sizing methods and tools
Initial calculation method Questionnaire without

Educated guess formulas
For structured questions
T-Shirt sizing
Simple algorithms with many
assumptions
Quick sizer
Supports user-based and
throughput-based sizing
Formulas
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 and Figures

 Available online since 1996
 New Special Quick Sizer version for SAP S/4HANA Cloud
 SAP HANA Quick Sizer version 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 HANA Standalone
– SAP BW/4HANA
– etc.
 Sizing by users and/or by throughput
Sizing and configuration
1 Create a Quick Sizer project and provide input on

the business usage/requirements of the customer
into the Quick Sizer project.
SIZING
2 The Quick Sizer tool calculates the sizing result

(memory, disk space and disk I/O, and CPU)
based on the input
Check the list of certified AnyDB or SAP HANA

3
hardware to see which hardware providers offer
hardware configurations that match the sizing result.
CONFIGURATION
Provide the sizing result (or the Quick Sizer project
4 number) to the hardware vendor and get proposal
for appropriate hardware configuration and prices.
Agenda
Sizing tools
Demo Quick Sizer

 Greenfield
 Migration

Demo
Quick Sizer
Two different/separate sizing strategies with different goals
Sizing by Users Sizing by Throughput
Advantages Advantages
 Users are relatively easy to  Scenario, transaction
determine  Based on actual business objects
 Memory is driven by user contexts and scenarios
 Peak/average sizing
Challenges
 Define “user” Challenges
 Determine user load patterns  Obtaining the right figures
 Sizing DB growth by users

Agenda
Sizing tools
Demo Quick Sizer

 Greenfield
 Migration

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:

Agenda
Sizing tools
Demo Quick Sizer

 Greenfield
 Migration

Greenfield sizing
New SAP HANA system

(Greenfield sizing)
Use Quick Sizer

Expert sizing for SAP
• SAP HANA version Sizing guidelines
• SAP S/4HANA Cloud version
HANA native
Methodology and sizing result Sizing document Services

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

Quick Sizer – SAP HANA version
special features
Quick Sizer – special features
Data Aging in SAP 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 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: SAP HANA memory result – 4,2 TB for SAP S/4HANA server (24 month residence time in memory)
Option 2: SAP HANA memory result – 8,9 TB for SAP S/4HANA server (no data aging)

SAP HANA Quick Sizer – special features
SAP 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.
The calculation of the disk I/O requirements with the SAP HANA Quick Sizer is now possible.

SAP HANA disk and memory areas – Overall picture
Memory Data Storage
Column Store Delta segment
Working Memory DRAM

NSE + Hybrid LOBs
NSE + Hybrid LOBs caches
Row Store Row Store
Persistent
Column Store (Column Memory
Loadable Main) (NVRAM)
Column Store (Column
Loadable Main)
Unloaded columns
LOG

Persistent memory
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

– SAP HANA-servers with Intel Cascade Lake CPUs
Calculation:
Persistent Memory: Amount of memory required for the column store data
DRAM: Total SAP HANA Memory – Persistent memory

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
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
Refer to the following 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.
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.
Refer to the following 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.
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
Measure resource consumption (CPU/Memory) and response times and
calculate the degree of parallelization
DB Response Time = 4 sec
DB CPU Time = 20 sec
𝐃𝐃𝐃𝐃 𝑪𝑪𝑪𝑪𝑪𝑪 𝒕𝒕𝒕𝒕𝒕𝒕𝒕𝒕 𝒐𝒐𝒐𝒐 𝒂𝒂 𝑸𝑸𝑸𝑸𝑸𝑸𝑸𝑸𝑸𝑸
𝑨𝑨𝑨𝑨𝑨𝑨. 𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝑫𝑫 𝒐𝒐𝒐𝒐 𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑 =
Avg. DoP = 5 𝐃𝐃𝐃𝐃 𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹 𝒕𝒕𝒕𝒕𝒕𝒕𝒕𝒕 𝒐𝒐𝒐𝒐 𝒂𝒂 𝑸𝑸𝑸𝑸𝑸𝑸𝑸𝑸𝑸𝑸
Memory per second runtime = 500 MB
Identify, how they will be used, e.g. filter criteria, authorizations and how
often they will be executed
Number of concurrent users = 216 Queries_per_sec = Number of users per user type *
Executions per hour per user = 50 Time spent on each query *
# queries per hour per user type /
Executions per sec per user = 3 3600
Avg. number of parallel = 216 * 100% * 50 / 3600
queries per sec = 12 = 3
Avg. number of parallel queries per sec

= Executions per sec per user * DB Runtime
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
= 3 * 4 = 12 38
Perform a forecast calculation based on the expected usage of the
queries/apps
Required Number of Threads = Avg. number of parallel queries *

Avg. Degree of Parallelization
= 12 * 5
= 60
Required Memory = Avg. number of parallel queries *

(Response_Time * Memory per second runtime / 2)
= 12 * (4 * 500/ 2)
= 12000 MB

User
Number of concurrent users 216
Exec per hour per user 50
Example Exec per hour

Exec per sec
10800
3
Avg. number of parallel queries per sec 12
Query
Snapshot DB Response Time 4
DB CPU Time 20
Avg. Degree of Parallelization 5
MB per second runtime 500
x x x 1
x x x 2
x x x 3
x x 4
x x 5
x x 6
x 7
x 8
x 9
10
11
12
3 3 3 3 3
2 2 2 2 2
1 1 1 1 1
3 3 3 3 3 3
3 3 3 3 3 3
2 2 2 2 2 2
2 2 2 2 2 2
1 1 1 1 1 1
1 1 1 1 1 1
3 3 3 3 3 3 3
3 3 3 3 3 3 3
3 3 3 3 3 3 3
3 2 2 2 2 2 2 2
2 2 2 2 2 2 2 2
1 2 2 2 2 2 2 2
3 1 1 1 1 1 1 1
3 1 1 1 1 1 1 1
2 1 1 1 1 1 1 1
2 3 3 3 3 3 3 3 3
1 3 3 3 3 3 3 3 3
1 3 3 3 3 3 3 3 3
3 3 3 3 3 3 3 3 3 3
2 3 2 2 2 2 2 2 2 2
1 3 2 2 2 2 2 2 2 2
3 2 2 2 2 2 2 2 2 2
3 2 2 2 2 2 2 2 2 2
2 2 1 1 1 1 1 1 1 1
3 2 1 1 1 1 1 1 1 1 1
2 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1

Quick Sizer – SAP S/4HANA Cloud
version special features
Sizing for SAP S/4HANA Cloud – Why?
User Metric
SAP
S/4HANA
Cloud
SAP HANA
Pricing
Memory

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

SAP S/4HANA Cloud available
The tool can be used for SAP 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
 Only two sizing KPI’s (SAP HANA RAM for Business
data & Frontend Network Load)
 Sizing of API calls

SAP S/4HANA Cloud QS significantly easier than SAP HANA – QS
Structure

SAP S/4HANA Cloud QS significantly easier than SAP HANA – QS
Results

Agenda
Sizing tools
Demo Quick Sizer

 Greenfield
 Migration

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, • Sizing report (note 229690) which runs on the source BW
anyOS) ABAP system to determine the required SAP HANA RAM and ABAP system to determine the required SAP HANA RAM and
disk on the new HANA-based solution disk.
• Potential areas for housekeeping, cleanup and archiving • Potential areas for housekeeping, cleanup and archiving
• In addition, a SAP HANA CPU requirement assessment is
• Report /SDF/HDB_SIZING (Modification 77) contains enhancement
included
for persistent memory sizing
• Persistent Memory sizing will be available soon
• 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
Back to Overview

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

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 an SAP HANA database.
The sizing report /SDF/SAP 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!

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:

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

Migration sizing part 2/2
Existing NW Java system to be migrated Existing Non-NW-based system to be

to SAP HANA migrated to SAP HANA
SAP HANA native SAP S/4HANA
•Analysis of legacy
•Analysis of legacy
Expert Sizing system
system
•SAP Note 1514966
Sizing Guidelines •SAP HANA version
•Request a sizing
of Quick Sizer
service

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

Agenda
Sizing tools
Demo Quick Sizer

 Greenfield
 Migration

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

SAP HANA TDI Phase 5: Workload-driven SAP HANA system sizing
Increased flexibility, lower TCO
The newly enhanced sizing approach for SAP HANA enables workload-driven hardware
configurations resulting in increased flexibility and new cost savings for customers
APPLIANCE DELIVERY MODEL SAP HANA TAILORED DATACENTER INTEGRATION (TDI)

PHASE 5
Pre-defined HW sizing Flexible HW sizing
(Applies only to newer processor types: Intel Xeon-SP Skylake*, Intel Xeon EX E7
 T-Shirt Sizing with best in class performance Broadwell*, and IBM Power8 processors)
 Highly optimized hardware setup (only top-bin  Tailored customer sizing: System memory & processor sizing
CPUs) are fine-tuned for the specific customer workload
Low Implementation effort  SAP HANA hardware partner translates the sizing results
(SAPS, RAM, CPU, and disk I/O**) into customer-tailored
 Pre-configured and pre-installed system setup system configurations using a wide range of CPUs (incl. lower-
end CPUs, not only top-bin CPUs)
Only hardware is delivered – Sizing and installation remains

the responsibility of customer and/or partner
*Platinum, Gold, Silver with 8 or more cores
** TDI storage KPI´s still need to be met but the I/O sizing takes a higher precedence: If workload requires more I/O
than the system / configuration has to be adjusted to meet the higher I/O requirements coming from sizing
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 HANA Quick Sizer (for greenfield sizing)

YouTube Video
* Requires login credentials

Continue your SAP TechEd 2019 Learning Experience
Join the digital SAP TechEd Learning Room 2019 in SAP Learning Hub
 Access SAP TechEd Learning Journeys

 Discover related learning content
 Watch webinars of SAP TechEd lectures
 Learn about SAP’s latest innovations with openSAP
 Collaborate with SAP experts
 Self-test your knowledge
 Earn a SAP TechEd knowledge badge

Engage with the SAP TechEd Community
Access replays and continue your SAP TechEd discussion after the event
within the SAP Community
Access replays Continue the conversation Check out the latest blogs
 Keynotes  Read and reply to blog posts  See all SAP TechEd blog posts
 Live interviews  Ask questions  Learn from peers and experts
 Select lecture sessions  Join discussions
http://sapteched.com/online sap.com/community SAP TechEd blog posts

More information
Related SAP TechEd Learning Journeys

 CAA3 – Move to SAP S/4HANA
 CAA4 – Get to SAP S/4HANA Cloud
Related SAP TechEd sessions

 LT103 – How the World’s Largest ERPs Move to SAP S/4HANA….
Public SAP Web sites

 SAP Community: www.sap.com/sizing
 SAP Community: www.sap.com/benchmarks

Thanks for attending this session.
Feedback Contact for further topic inquiries

Please complete your session evaluation Sebastian Schmitt
for CAA303. Product Management Performance & Scalability
sebastian.schmitt@sap.com
Detlef Thoms
Product Management Performance & Scalability
detlef.thoms@sap.com
Appendix
What Is 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

Demo
Quick Sizer
Two different/separate sizing strategies with different goals
Sizing by users Sizing by throughput
 Text
Advantages Advantages
 Users are relatively easy to  Scenario, transaction
determine  Based on actual business objects
 Memory is driven by user contexts and scenarios
 Peak/Average sizing
Challenges
 Define “user” Challenges
 Determine user load patterns  Obtaining the right figures
 Sizing DB growth by users

Creating a sizing project
Procedure
1. Find your customer number as
default
2. Enter a project name
3. Read and accept the disclaimer

Details on Quick Sizer start page
If you want to create a new project

→ Create Project
If you want to change an existing project

→ Change Project
If you want to display a project

→ Display Project
If you want to get an overview about Quick Sizer

→ Quick Sizer for Beginners
If you want to copy your project

→ Create with reference function
If you forgot the project name

→ Project search function ‘Show my Projects’
If you want to take a look at an example for a application

→ Show examples function
Structure of Quick Sizer
Project-wide
information
• Workdays
• Status
• Owner
• Method
• Links to hardware
vendors
Input • Documentation
Navigation Questionnaire • Disclaimer
Tree • Hardware infrastructure (optional)
• Solutions • Per solution/key capability
• Key
capabilities

Navigation
To open a questionnaire, click on the text
Meaning of the icons:

 Grey: no input yet
 Green: questionnaire filled in, no errors
 Yellow light bulb: current questionnaire
 Red: questionnaire filled in and contains errors
– If there are errors, no results will be calculated

Navigation — Search

Project header information
Functions in the project header

• Saving of sizing data
• Create print page for each page
• Calculate result
• Set project to GoingLive and Final
• Feedback
• Quick Sizer tool documentation
• Direct access to hardware vendors sizing information
• Disclaimer

Project header information (cont.)
 Change the number of workdays per year
Status
• Empty project (Without entries)
• In progress
• GoingLive
• In progress after GL
• Final
• Inactive
Owner
• Displays GL version or customer version
Method

Details on project header information
Documenting sizing projects: Print files
Print files
• From every page on Quick Sizer, you can create a print file
• Print directly
• Save to disk
• Helpful for status documentation

Details on help and online documentation
Quick Sizer tool documentation

• General documentation on Quick Sizer
How to fill in the questionnaire

• Help per questionnaire

Structure of sizing questionnaires
Questionnaire-wide information
User-based sizing
Throughput-based sizing

Details and questionnaire-Wide information
Changing average workday and peak times

• Default workday: 9-18
• Default peak: 12-13
Check input
Use default values
More Details
Clear questionnaire
Link How to fill in the questionnaire

User-based sizing
Concurrently active users
Standard pattern of low, medium, and high activity users
If disk is calculated, you also need to enter the residence time in

months
Independence of results

User-based sizing tables
Clear and mark functions

Input fields and functions

Throughput-based sizing
Functions in the input tables

• Tray
• Mark lines
• Delete/Clear
Entry fields/non-entry fields/mandatory input fields

Throughput-based sizing tables
Table selection menu

 Element
 A/P – (A)verage or (P)eak
 TI – Time interval
 Objects – Number of objects
 Items
 % chg / % dsp – changes & displays in
%
 Mon. – Months – Residence time in
months
 Arch. – Archiving project planned
 S.t. / E.t – Begin and end of
processing times
 ID – Identification
 Short text – Text field for comments

Error handling – Check function and messages

Errors – No sizing result

Details on result display/result level
Result levels
• Project
• SAP solution
• Software component
• Key capability
• Sizing elements + choice
• Line results + inputs
• Results, statistics, inputs

Sizing categories and results – I/II
There are the following sizing categories and results for Memory, CPU, and Disk space:
Note
The results of category XXL may be outside the scope of the Quick Sizer tool, please contact your hardware
vendor or SAP for further information.
Note
Please keep in mind that the sizing categories for CPU, Disk space and Memory have to be considered as
disjoint result categories (no interdependency between the different sizing categories);
Sizing categories and results – II/II
There are the following sizing categories and results for Data IO and Log IO:
Note
The results of category XXL may be outside the scope of the Quick Sizer tool, please contact your hardware
vendor or SAP for further information.

SAP HANA appliance vs. SAP HANA tailored data center integration
SAP started delivering SAP HANA in the form of standardized and SAP HANA tailored data center integration provides you with
highly optimized appliances, offering companies the possibility to flexibility regarding the hardware components required to run SAP
choose between several SAP HANA hardware partners. HANA.
Those SAP HANA appliances are built based on a well-defined Leveraging this approach you will:
hardware specification designed for the performance requirements – Reduce hardware and operational costs by reusing existing hardware
of a solution which leverages in-memory technology. components and operation processes
– Mitigate risks and optimize time-to-value by enabling existing IT management
It is a delivery of a preconfigured hardware setup with preinstalled processes for SAP HANA implementations
software packages that can be quickly implemented by your SAP – Have more flexibility in hardware vendor selection by leveraging the existing
HANA hardware partner of choice. ecosystem

Follow us
www.sap.com/contactsap
© 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.

CAA303 Presentation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CAA303 Presentation

Uploaded by

Copyright:

Available Formats

Sizing for

SAP S/4HANA and SAP S/4HANA Cloud

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

Complete the session evaluation for this session

Download the app from

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

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

Sizing introduction and basics

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA

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

Sizing introduction and basics

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud

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

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

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

Single user – Quality and implications of accesses to

– Equivalent to multi-user test, stress test,

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

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

Hardware budget sizing Advanced sizing

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

Sizing is the joint responsibility of

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

 Challenge to obtain sufficient usage information as sizing

 Insufficient sizing input is compensated by assumptions,

 While it is perfectly ok to work with assumptions you must

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

Sizing introduction and basics

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud

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

* Requires login credentials

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

Initial calculation method Questionnaire without

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

Facts and Figures

1 Create a Quick Sizer project and provide input on

2 The Quick Sizer tool calculates the sizing result

Check the list of certified AnyDB or SAP HANA

Sizing introduction and basics

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud

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

Sizing by Users Sizing by Throughput

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

Sizing introduction and basics

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud

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

Use SAP HANA Quick Sizer Use Migration reports/ procedure

Certified and Supported SAP

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

Sizing introduction and basics

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud

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

New SAP HANA system

Use Quick Sizer

Methodology and sizing result Sizing document Services

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

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

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