SAP HANA Migration Sizing
This documents shows the different sizing methods and tools for migration sizings. Download the DocumentPublic
Migration (Brownfield)
Sizing
SAP HANA
Performance & Scalability, SAP
November, 2023
Migration (Brownfield)
Sizing
SAP HANA
Performance & Scalability, SAP
November, 2023
2Public
Sizing introduction and basics
Migration Sizing SAP HANA
Agenda
Sizing introduction and basics
Migration Sizing SAP HANA
Agenda
3Public
Performance requirements: Sizing
Sizing-relevant KPIs (Key Performance Indicators)
• From a customer perspective, sizing is the translation of business requirements (business throughput
and user concurrency requirements) into hardware requirements.
• From an SAP development standpoint, sizing refers to the creation of a sizing model for the product
functionality with a reasonable number of input parameters and assumptions. The goal is to define a
sizing guidance for each SAP application.
• The sizing procedure helps customers determine the resources (CPU, memory, data growth on disk, disk
I/O and frontend network) required by an application within the customer's business context. For on-
premise applications the sizing procedure is publicly available.
• Sizing is not configuration: Actual system configuration is a task performed by the hardware vendor or the
Infrastructure as a Service Provider who must ensure the system landscape meets the hardware
requirements determined by sizing.
Performance requirements: Sizing
Sizing-relevant KPIs (Key Performance Indicators)
• From a customer perspective, sizing is the translation of business requirements (business throughput
and user concurrency requirements) into hardware requirements.
• From an SAP development standpoint, sizing refers to the creation of a sizing model for the product
functionality with a reasonable number of input parameters and assumptions. The goal is to define a
sizing guidance for each SAP application.
• The sizing procedure helps customers determine the resources (CPU, memory, data growth on disk, disk
I/O and frontend network) required by an application within the customer's business context. For on-
premise applications the sizing procedure is publicly available.
• Sizing is not configuration: Actual system configuration is a task performed by the hardware vendor or the
Infrastructure as a Service Provider who must ensure the system landscape meets the hardware
requirements determined by sizing.
4Public
SAP HANA Sizing KPIs
▪ 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
SAP HANA Sizing KPIs
▪ 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
5Public
Memory: Leading Driver for SAP HANA Sizing
• The main driver for memory sizing is the table data of the planned SAP HANA system
• Most tables are located in the highly compressed column store of SAP HANA
• For working memory (or work space or temporary memory) of the database and temporary calculations,
almost the same size as for table data is required additionally
• A SAP HANA database includes further memory areas, such as code, stack, caches, operating system, and
other system files. These areas are typically small compared to a typical database.
Memory: Leading Driver for SAP HANA Sizing
• The main driver for memory sizing is the table data of the planned SAP HANA system
• Most tables are located in the highly compressed column store of SAP HANA
• For working memory (or work space or temporary memory) of the database and temporary calculations,
almost the same size as for table data is required additionally
• A SAP HANA database includes further memory areas, such as code, stack, caches, operating system, and
other system files. These areas are typically small compared to a typical database.