Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

SAP HANA Sizing

Download as pdf or txt
Download as pdf or txt
You are on page 1of 23

SAP HANA Sizing

www.sapbuddy.com
HANA Installation Preparation

Requirement Deployment Hardware


HANA Sizing
Scoping Planning Identification

Infrastructure Post
Pre-requisite Installation
Planning Installation

www.sapbuddy.com
Requirement Scoping
• Identify SAP Products, components and versions
Product Stack • Determine HANA System and version
• Integration requirements

• Gather Landscape requirements – Non Prod, Prod


Landscape • Scalability and availability requirements
• Size and growth requirements

Deployment • Define landscape and HANA deployment scenario

Scenario • On-premise / Cloud / Virtualization etc

• Gather application and HANA sizing inputs


Sizing • Initial and ongoing growth parameters

www.sapbuddy.com
Sizing SAP HANA Concept
• SAP HANA customer must perform a memory sizing
• New SAP HANA implementations
– SAP Quick Sizer
• Systems that are migrating to SAP HANA
– Migration is from an SAP NetWeaver
• Use sizing report on the source database
– Migration is from a non-SAP NetWeaver
• use the sizing as in SAP Note 1514966
• Any system that is large or complex
– SAP sizing expert
www.sapbuddy.com
Sizing SAP HANA basics
• Sizing of the SAP HANA database is based mainly on the
required main memory size.
• The memory size is determined by the amount of data that is to
be stored in memory
• SAP HANA compresses the data.
– depends on the used scenario, you cannot estimate the amount of
memory needed
– The memory sizing must always be performed using the Quick Sizer
for SAP HANA , or the SAP HANA Sizing Reports and SAP Notes.

www.sapbuddy.com
SAP HANA Sizing Scenarios
Scenario SAP BW/4HANA SAP HANA Non-NetWeaver
New Implementation Quick Sizer Quick Sizer Sizing guide as available
for SAP BW/4HANA for Suite on SAP HANA
Database SAP Note 1637145: Sizing for SAP Note 1514966 – SAP HANA 1.0 : SAP Note 1514966: SAP
migration SAP BW on HANA Sizing SAP HANA HANA: Sizing SAP In- Memory
Database
SAP Note 1736976 : Sizing SAP Note 1793345: Sizing for SAP
Report for SAP BW on HANA Suite on SAP HANA

SAP Note 2121330 - FAQ: SAP SAP Note 1872170: Suite on SAP
BW on HANA Sizing Report HANA memory sizing report

SAP Note 2296290 - New Sizing SAP Note 2367595 - Suite on HANA
Report for BW/4HANA memory Sizing

www.sapbuddy.com
HANA Sizing Methodology

www.sapbuddy.com
SAP Quick Sizer
Go to →
https://www.sap.com/about/benchmark/sizing.html → Quick Sizer → HANA version → Create Project

www.sapbuddy.com
SAP Quick Sizer Tool

www.sapbuddy.com
SAP Quick Sizer
• Calculate Results

www.sapbuddy.com
Sizing Approach
• SAP In-Memory Appliance
– Certified SAP HANA appliances
– https://www.sap.com/dmc/exp/2014-09-02-hana-
hardware/enEN/index.html

• Tailored Datacenter Integration (TDI)


– To use available hardware
– To reuse hardware and save costs

www.sapbuddy.com
Sizing HANA Tailored Data Center Integration Setup
• RAM sizing for static and dynamic data
• Disk sizing for the persistence storage
• CPU sizing for the queries and calculations

www.sapbuddy.com
Main Memory Sizing
• Sizing Report
– SAP Quick Sizer: http://service.sap.com/quicksizer
– SAP Note 1514966: SAP HANA: Sizing SAP In-Memory Database
– SAP Note 1637145: Sizing for SAP BW/4HANA
– SAP Note 1736976 : SAP BW/4HANA Sizing Report
– SAP Note 1793345: Sizing for SAP Suite on HANA
– SAP Note 1872170: Suite on SAP HANA Memory Sizing Report
– SAP Note 2055470: SAP HANA on POWER Planning and Installation
Specifics – Central Note

www.sapbuddy.com
Sizing for Suite on SAP HANA Using SAP Notes
1793345 and 1872170

www.sapbuddy.com
Sizing for SAP BW/4HANA Using SAP Notes
1637145 and 1736976

www.sapbuddy.com
HANA Main Memory Sizing Approach
• Determine static + dynamic RAM requirement
– Calculate “uncompressed” data volume to be loaded into HANA
(tools provided)
– Apply compression factor (from attachment to sizing notes)
– Multiply result by 2 because we recommend
RAM dynamic = RAM static

www.sapbuddy.com
Static vs. Dynamic Memory Requirements
• Static data memory requirements
– RAM requires to the amount of main memory used for holding the
table data

• Dynamic data memory requirements


– Additional memory for objects that are created dynamically when
new data is loaded or queries are executed

www.sapbuddy.com
Disk Sizing
• While Sizing a HANA system, consider the disk requirements including
the following:
• Persistence area (Data Volume + Log volume)
– Software
– Configuration
– Logs and Traces
• Space for BACKUPS
– Data backup
– Log backup Each Backup Size >= Data Size + Redo Log Size
– Full backup
-> Consider multiple backup sets to be retained in the disk
-> Consider compression where possible
-> Move backups to external medium/storage through backup tools
www.sapbuddy.com
Disk Sizing
Disk Space Required for the Data Volume
/hana/data/<SID>

Disk Space Required for the Log Volume


Examples: Log Volume Size
● 128 GB system ≥Size log volume = 64 GB
● 256 GB system ≥Size log volume = 128 GB
● 512 GB system ≥Size log volume = 256 GB
● 1 TB system ≥Size log volume min = 512 GB
● 2 TB system ≥Size log volume min = 512 GB
● 4 TB system ≥Size log volume min = 512 GB
/hana/log/<SID>

www.sapbuddy.com
Disk Space Required for SAP HANA Installation
Examples: Single Size node
● Single-node 128 GB ≥Size installation = 128 GB
● Single-node 256 GB ≥Size installation = 256 GB
● Single-node 512 GB ≥Size installation = 512 GB
● Single-node 1 TB ≥Size installation = 1 TB
● Single-node 2 TB ≥Size installation = 1 TB
● Single-node 4 TB ≥Size installation = 1 TB
Examples: Scale out HANA installation
● 3+1 system, 512 GB per node ≥Size installation = 1x 512 GB = 512 GB
● 4+1 system, 512 GB per node ≥Size installation = 1x 512 GB = 512 GB
● 5+1 system, 512 GB per node ≥Size installation = 2x 512 GB = 1 TB
● ...
● 9+1 system, 512 GB per node ≥Size installation = 3x 512 GB = 1.5 TB
● ...
/hana/shared/<SID> ● 3+1 system, 1 TB per node ≥Size installation = 1x 1 TB = 1 TB
● 4+1 system, 1 TB per node ≥Size installation = 1x 1 TB = 1 TB
● 5+1 system, 1 TB per node ≥Size installation = 2x 1 TB = 2 TB
● 9+1 system, 1 TB per node ≥Size installation = 3x 1 TB = 3 TB

www.sapbuddy.com
Disk Space Required for Backups

• Complete backup contains entire payload of all data volumes


• Backup directory also depending on number of backup generation on disk

www.sapbuddy.com
DB CPU Sizing
• Sizing approach similar to user based CPU sizing of BW and BWA
• Maximize query throughout by multiuser scenarios with queries of
different complexity out of delivered content, 10-20 million records
• Assumptions:
– Three different query complexity classes
– Three different user profiles (click rate, query complexity)
• Normalization of query throughout per core resp, active per core:
– CPU:300 SAPS per active user / 0.65 for a CPU utilization buffer
– Note the CPU sizing has to be adjusted so that the server load does not
exceed 65% in average.

www.sapbuddy.com
www.sapbuddy.com

You might also like