Professional Documents
Culture Documents
CAA303 Presentation
CAA303 Presentation
CAA303 Presentation
Las Vegas
September 24–27, 2019
Detlef Thoms
Barcelona
October 8-10, 2019
Sebastian Schmitt
Bangalore
November 13-15, 2019
Sukshatha Rao
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.
Sizing tools
Sizing tools
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.
“
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
Performance predictions
Multi user test for high volume environment
(Volume)
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)
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
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
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13
Risks in a sizing project
CUSTOM CODING & Are very hard to predict: Make sure there is a verification
SPECIAL DATA process
CONSTELLATIONS Make sizing measurements, if required
Sizing tools
Guidelines
Access sizing guidelines
Access sizing-related materials
Tools
Access quick sizer *
Sizing decision tree
Others
Training opportunities
FAQs
T-Shirt sizing
Simple algorithms with many
assumptions
Quick sizer
Supports user-based and
throughput-based sizing
Formulas
Simple or more
complex
Characteristics
Structured sizing questionnaires
Input for
– Greenfield sizing
– GoingLive Check
Hardware vendor contact list
Scope
SAP Key applications
– SAP S/4HANA
– SAP HANA Standalone
– SAP BW/4HANA
– etc.
Sizing by users and/or by throughput
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19
Sizing and configuration
Sizing tools
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
Sizing tools
Customer interested
in SAP HANA
New SAP HANA system Existing SAP system migrated to SAP HANA
(Greenfield sizing) (Migration sizing)
Sizing tools
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.
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 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.
Persistent
Column Store (Column Memory
Loadable Main) (NVRAM)
Column Store (Column
Loadable Main)
Unloaded columns
LOG
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.
Calculation:
Persistent Memory: Amount of memory required for the column store data
DRAM: Total SAP HANA Memory – Persistent memory
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.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 35
Quick Sizer – special features
Sizing SAP S/4HANA Embedded Analytics - Brownfield
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.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 36
Steps for an expert sizing
Activity
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
Decide whether optimizations are necessary and if yes analyze and optimize expensive queries and
5
retest
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 37
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 𝐃𝐃𝐃𝐃 𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹𝑹 𝒕𝒕𝒕𝒕𝒕𝒕𝒕𝒕 𝒐𝒐𝒐𝒐 𝒂𝒂 𝑸𝑸𝑸𝑸𝑸𝑸𝑸𝑸𝑸𝑸
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
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
User Metric
SAP
S/4HANA
Cloud
SAP HANA
Pricing
Memory
Sizing tools
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
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 48
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.
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.
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!
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:
•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
SAP Note
SAP Note Early Watch SAP Note 1969700
1872170 Alert 2296290 SAP Note
1698281
Sizing tools
Virtualization – 1788665 - SAP HANA Support for virtualized / partitioned (multi-tenant) environments
The newly enhanced sizing approach for SAP HANA enables workload-driven hardware
configurations resulting in increased flexibility and new cost savings for customers
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)
www.sap.com/sizing
Access to Quick Sizer*
Access to sizing guidelines, for example, SAP HANA accelerators
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
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
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
Procedure
1. Find your customer number as
default
2. Enter a project name
3. Read and accept the disclaimer
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
Status
• Empty project (Without entries)
• In progress
• GoingLive
• In progress after GL
• Final
• Inactive
Owner
• Displays GL version or customer version
Method
Print files
• From every page on Quick Sizer, you can create a print file
• Print directly
• Save to disk
• Helpful for status documentation
Questionnaire-wide information
User-based sizing
Throughput-based sizing
Check input
More Details
Clear questionnaire
Result levels
• Project
• SAP solution
• Software component
• Key capability
• Sizing elements + choice
• Line results + inputs
• Results, statistics, inputs
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);
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 86
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 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
www.sap.com/contactsap