Professional Documents
Culture Documents
Hop - Sizing and Hardware Planning Mar2017
Hop - Sizing and Hardware Planning Mar2017
Hop - Sizing and Hardware Planning Mar2017
Kent Wang
BP Technical Enablement, IBM Systems
March 2017
SAP HANA on IBM POWER
Agenda
Note that the following presentation does not cover HANA 2.0 sizing and hardware planning.
Refer to HoP - SAP HANA 2.0 Presentation Module
Business Applications
HANA
Middleware
OS
IBM POWER8
Virtualization SYSTEM SOLUTIONS
Storage Virtualization
Storage
3 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
UPDATED 07/03/2016
HANA on POWER Building Blocks OSS 2133369 / 2227464 / 2218464
Business Warehouse
HANA SPS
(Support Package SPS09 SPS10 SPS11
Stack)
Technical Stack
Production Non Production
4 x 8GB FC Ports
Storage Xfs w/ multipath NPIV (TDI or internal disk) Xfs, NFS, GPFS and ext3
RAM
based on 6144 64
CORES
48
this is an older 4096
chart and
3072 32
shows 8 vs 4
min cores per 2048
16
LPAR. 1024
0 0
E880 E870 E850 S824L S824 S822L S822
Min Cores 8 8 8 8 8 8 8
Max Cores 96 80 32 24 24 24 20
MIN Ram 128 128 128 128 128 128 128
BW SPS09 Max RAM 3072 2560 1024 768 768 768 640
BW SPS10 Max RAM 3072 2560 1024 768 768 768 640
BW SPS11 Max RAM 4800 4000 1024 768 768 768 640
BS Max RAM 9216 7680 3072 2304 2304 2304 1920
SERVER MODEL
8 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
UPDATED 07/03/2016
HANA on POWER Building Blocks OSS 2230704
Production Systems: Multiple LPARS per physical host – with at least one production system.
Virtualization PowerVM. Dedicated or Dedicated Donating for PRD. Shared Processor Pools for n-PRD.
VIO Optional and excluded from the above lpar count (Recomended: Dedicated Donating).
Changes
No Changes
Frontends New infrastructure
At frontends mandatory to run SAP
At application server HANA
infrastructure Different sizing for
Application Servers
=> HANA infrastructure
Any OS
Re-use of available Migration of database
APP APP APP APP
application servers to SAP HANA required
Sizing of application
servers remains Partly necessary
valid Data model adoptions
Any DB / HANA migration HANA / Custom extensions
Any OS Linux
Overview
Hardware Design
SW Setup
Compliance Verification
Sizing Factors:
– Memory (Dominant factor)
– CPU (No of cores is dependent on the Memory Size of HANA Node/LPAR)
Sizing Approach
– For Migration Sizing, SAP provides two different Sizing Reports (BW or SoH).
• For both reports an ABAP runs on the existing SAP System and creates a
sizing document.
• The content of both sizing documents provides a detailed description of
HANA DB memory requirements.
– Each Initial Sizing should be done using the HANA version of the SAP
Quicksizer (mandatory)
– Rule of thumb.
• HANA needs about 50% the size of an existing classic DB for its memory
Example: DB = 1TB, HANA Node/LPAR size = 500 GB
15 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
Sizing Process and Workflow
17 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
Migration Sizing
HANA Sizing Components Overview
This table shows where to get sizing estimates, depending on the Sizing Scenario. © 2017 IBM Corporation
18
IBM Internal and Business Partner Use Only
SAP HANA on IBM POWER
CPU Sizing by Core to Memory Ratios
• The primary sizing factor for HANA is the Memory (RAM).
• Of course the HANA DB Node needs CPU capacity as well.
• At the current HANA DB CPU sizing the CPU requirement is related to the DB Mem size.
• As larger the Database as lager the RAM as more CPU is need.
• The calculation method used is the so called “Core to Memory” ratio (CtM).
https://www.ibm.com/partnerworld/wps/sizing/protect/sizingguide/ViewSG?guide_id=sgq84752020041706102
24 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
Migration Sizing - Business Warehouse Example
25 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
Migration Sizing:
Business Warehouse Example w/ Report
OSS Note: 1736976 - Sizing Report for BW on HANA
26 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
Migration Sizing
Sizing Report for Business Warehouse on HANA (Multi Node)
OSS Note: 1736976 - Sizing Report for BW on HANA
POWER8: Each node has a maximum RAM size below or equal to the maximum RAM allowed per LPAR.
Please refer to SAP note 2188482 for details.
POWER8: The sum of total RAM of the nodes participating is equal or bigger than the value of 'Memory
Requirement (Minimum Total)' from the sizing report.
About the size …
– Calculated in ABAP
– Based on Sample Data
– Omits indexes, temporary
space, …
Memory Sizing Selected Node Size
27 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
Rule of Thumb sizing for Business Warehouse
RAW DATA
[2.5TB]
COMPRESSED
MEMORY
OLAP DATA 0.5:1
[1TB]
[512 GB]
As a rule of thumb, physical HANA memory requirements are approximately 0.5*Raw DB Size
28 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
Points to Note on Sizing Reports
• Scale Up and Scale Out
– Scale Up: HANA DB fits into one Node/LPAR
– Scale Out: HANA DB does not fit in one Node/LPAR must be distributed over
several LPARs / also if the memory requirement is higher than the preselected
memory size
– To avoid Scale Out sizing report, choose the largest possible Node size (saves
50GB of cache per server)
– The BW sizing report allows analyzing of existing HANA systems, verifies sizing
estimates pre- and after migration and helps migration to other Nodes or LPARs
– Initial Sizing = Sizing from scratch (also called Greenfeld sizing)
– Initial Sizing of HANA DB can be done by SAP or experienced IBMer usually with
the HANA version of the SAP Quicksizer (QS)… https: //service.sap.com/quicksizer
– For SAP HANA server memory sizing you need input on the Quicksizer tables 5 + 6
(InfoCubes (Cube) and DataStore Objects (DSO) )
29 © 2017 IBM Corporation
IBM Internal and Business Partner Use Only
SAP HANA on IBM POWER
BW/4 HANA Migration
• BW/4 HANA Initial Sizing
– Have information on the largest InfoProviders of the planned systems (record
structures, line counts)
– Create a SAP Quicksizer project, HANA version – select “SAP NetWeaver BW
Powered by SAP HANA” and enter values into the Quicksizer form
– Use only table 6 for DSO objects to enter information on InfoProviders
– Do not use table 5 (InfoCubes).
– The Quicksizer result can be used as an estimate for the BW/4 HANA system
• BW/4 HANA Migration Sizing
– Refer to note 2296290 and derive sizing requirements for the current BW system
running on BW on HANA sizing report /SDF/HANA_BW_SIZING
– Sizing results can be used to estimate the resource requirements for the BW/4
HANA system as well
30 © 2017 IBM Corporation
IBM Internal and Business Partner Use Only
SAP HANA on IBM POWER
Migration Sizing - Suite on HANA Example w/ Report
OSS Note: 1872170 - Suite on HANA - S/4 sizing report
Memory Sizing
31 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
Migration Sizing - Suite on HANA Detailed Report
OSS Note: 1872170 - Suite on HANA - S/4 sizing report
Hybrid LOB: Large Object (LOB) is a data type used to store large records (Typically texts,
images, audio, …) and is often not well compressed. By default, columns of data type LOB are
no longer fully loaded to memory on first access. Consequently only LOB data which is needed,
is loaded to memory. For sizing, the assumption is made, by the report that 20% of the Data
stored on disk can be loaded to memory at the same time.
Anticipated requirement
after clean up shows the
memory consumption that
can be achieved if some
data volume management
projects are implemented
on the system. (Data
Aging, …)
Example does not include
growth or OS
32 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
HANA Storage Sizing
– Backups. Regularly scheduled backups are written to storage in configurable block sizes up to 64 MB.
• 𝑆𝑖𝑧𝑒𝑏𝑎𝑐𝑘𝑢𝑝𝑠 ≥ 𝑆𝑖𝑧𝑒𝑑𝑎𝑡𝑎 + 𝑆𝑖𝑧𝑒𝑟𝑒𝑑𝑜𝑙𝑜𝑔
– Data. SAP HANA persists a copy of the in-memory data, by writing changed data in the form of so-called savepoint
blocks to free file positions, using I/O operations from 4 KB to 16 MB (up to 64 MB when considering super blocks)
depending on the data usage type and number of free blocks. Each SAP HANA service (process) separately writes to
its own savepoint files, every five minutes by default.
• 𝑆𝑖𝑧𝑒𝑑𝑎𝑡𝑎 = 1.2 ∗ 𝑛𝑒𝑡 𝑑𝑖𝑠𝑘 𝑠𝑝𝑎𝑐𝑒 𝑓𝑜𝑟 𝑑𝑎𝑡𝑎 Use Sizing Reports
– Redo Log. To ensure the recovery of the database with zero data loss in case of faults, SAP HANA records each
transaction in the form of a so-called redo log entry. Each SAP HANA service separately writes its own redo-log files.
Typical block-write sizes range from 4KB to 1MB.
• 𝑆𝑌𝑆𝑇𝐸𝑀 ≤ 512𝐺𝐵 𝑆𝑖𝑧𝑒𝑟𝑒𝑑𝑜𝑙𝑜𝑔 = 1.2 ∗ 𝑅𝐴𝑀
As a rule of thumb, disk size = ~2 x RAM (assuming 1 copy of Backup)
• 𝑆𝑌𝑆𝑇𝐸𝑀 > 512𝐺𝐵 𝑆𝑖𝑧𝑒𝑟𝑒𝑑𝑜𝑙𝑜𝑔(𝑚𝑖𝑛) = 512𝐺𝐵
34 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
Storage Configuration Guidelines
Storage and SAN-Adapters have to be configured to comply with SAP Tailored Data Center Integration
(TDI) performance KPIs. (Min 8GB SAN Adapters).
Disk sizing / layout as HANA-DB persistency is not volume, but I/O driven.
Overall disk capacity is dominated by the number of DB-backups kept on disk.
A mix of HDD for DATA and SSD for LOG is used, see:
– SAPmagic Tool
– Storage Architecture and Configuration Guide for SAP HANA TDI
Non-Production and less performance critical systems can be built using internal disks.
Recommended IBM Storage System Combinations (Production):
Storage
Virtualization SAP HANA data SAP HANA log SAP HANA data SAP HANA log
System
FlashSystem /
SVC Storwize Storwize HDD SSD
(Storwize)
FlashSystem / DS8000 HDD SSD
SVC XIV
(XIV)
DS8800 / XIV Module Module
SVC DS8800
(FlashSystem)
SVC FlashSystem FlashSystem Flash
Flash Card Flash Card
System
35 IBM Internal and Business Partner Use Only © 2016 IBM Corporation
SAP HANA on IBM POWER
Storage Type for DATA Storwize V7000 Storwize V7000 Number of SVC nodes (pairs) 4 (2)
Storage Type for LOG FlashSystem 820 20TB FlashSystem 820 20TB Number of Storage Systems for DATA 4
Use same system for DATA and LOG No FALSE Number of disks per Storage System for DATA 64
Use SVC Stretched-Cluster
Number of HANA nodes 8 Number of Storage Systems for LOG 2
RAM per HANA node [in GB] 1024 Number of disk per Storage System for Log n/a
Type of Disk for DATA HDD 10K, 900GB, 2.5"
Type of Disk for LOG n/a
37 © 2017 IBM Corporation
IBM Internal and Business Partner Use Only
SAP HANA on IBM POWER
The following are useful guides to assist in sizing your SAP HANA Solution on IBM Systems:
• SAP HANA on IBM Power Systems and IBM System Storage – Guides
– Techdocs: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102502
• IBM System Storage Architecture and Configuration Guide for SAP HANA TDI (tailored
datacenter integration) V2.10
– Techdocs: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102347
• IBM System Storage sizing guideline for SAP HANA TDI, V3.1
– Techdocs: http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10859
• SLES 11.x for SAP Applications Configuration Guide for SAP HANA (x86 and POWER)
– Attached to SAP Note 1944799 –
“SAP HANA Guidelines for SLES Operating System Installation”
• Also look for the latest SAP HANA Notes on the SAP Site.
• Sizing and hardware planning for SAP HANA is a moving target as specifications continually
change with product announcements and testing results
• It is essential that any sizing be checked with the latest test results, sizing tools and SAP
Notes
End of Module 7
Thank You
Storwize FlashSystem
Spectrum Virtualize XIV FlashSystem
(SVC) DS8800 FlashSystem
FlashSystem FlashSystem