Ra Gace oat eed Principles of SAP HANA Sizing — on premise and cloud ‘Sebastian Schmitt, SAP rwceesrun SODisclaimer This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAPs strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document 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. SAP assumes no responsibility for errors or omissions in this document, except it such damages were caused by SAP intentionally or grossly negligent.Agenda Sizing Introduction and BasicsSAP HANA Sizing KPIs - Game Changer c= + Momory sizing is determined bythe data footprint in SAP HANA [business and meta dala in colimn and row store) | wemory )) Memory is aso used by other components (¢.9. SAP HANA caches) and or processing of requests “Congr nO, rr CPU pve eaued oy cou C+D)“ Semiterrtamc apees inte Senses ~ oud ta pres ad ogg dat @)_Psksie +)“ Setcntto peter andre pera Disk VO with acceptable data throughput and storage system latency. Frontend |) -Nawakszing ypealy ecusason ha bandit ands Network Load described in gigabits per second (gbps) Diferent sizing approach: SAP HANA sizing vs. sizing of traditonal DB Memory isthe leading driver for ‘SAP HANA sizing Massive parallelization in analytical scenarios will have an influence on Response Times; hhence CPU requirement wll get ‘more important for analytical scenarios Mixed transactional and analytic workloads now possible with SAP HANA but ‘compet for shared resources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 of the database and temporary calculations, almost the same size as for table data is required additionally * ASAP 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. Source DB ]Different Types of Sizing Hardware Budget Sizing Advanced Sizing = Very simple algorithms = Assumptions, likelihoods * Questionnaires, formulas = Level seting of project * Usage of standard tools é = «= Fisk identification + Focus on core business tech Qk Se processes * Throughput estates Greenfield sizing aft Smaler companies Neu large companies Re- / Delta / Upgrade Sizing tm = SAP system monitors = Goal: Extend an existing system by load / function Productive sizing Beare eeu a ~ Re:Sizing: Customer want 0 add 100 adional users whl do the same orate asthe current productive ones. ~ Delta Sizing: Customer's Ive wth CRM and want add SCM ~ Upgrade Siang: Customer want to upgrade to latest EMP Expert sizing Expert Sizing Large or complex projects * Additonal guidelines * Custom calculations * Analysis of custom coding * Custom sizing guidelinesThree-Party Collaboration Model Hardware Vendors Contributions * Ceniied benchmarks > Scalabie harware + itfrent contguratons ‘ogeer wih technology patines + Service level agreements + Final responsbiy for sizing at customer ste Sizing Recommendation + CPU SAPS) Memory (G8) Database space (63) Disk iO operations per see Frontend banawicth mips. ‘SAP ‘Contributions * Development and provision of bencimart oolets Regression testing ler naw roieoses ‘Standard sizing guidelines Sizng vetieaton processes ‘Customer Expectations from benchmarking and sizing + Optimal peioomance + Suggestion for HW contg Contributions Response ime requirements + Throughput requirements + Proves busines input Sizing is the joint responsibility of customer (LOB), SAP and HW Vendor. But The main responsibility have the HW Vendor. They have to make sure that the SAP software runs smoothly at customer site and that customers don't run into performance or TCO issues due to under-sized or over- sized HW. Examples: = Custom coding = Different businesses require different sizings = Ditferent applications need different amounts of CPUs: = Additional needs might come from additional not sized usagesRisks in a Sizing Project + Challenge to obtain sufficient usage information as sizing input INCOMPLETE INPUT * Often caused by communication issues DATA * Insufficient sizing inputs compensated by assumptions, which should be documented NOT VERIFIED ensure that a verification process is included in the project ASSUMPTIONS ARE => + While itis perfectly ok to work with assumptions you must plan Risks SPECIAL DATA process CUSTOM CODING & » Are very hard to predict: Make sure there is a verification CONSTELLATIONS => * Make sizing measurements, if requiredAgenda Sizing Tools and ResultsOfficial SAP Sizing Page: Guidelines © Access Sizing Guidelines + Access Sizing-related Materials, Tools + Access Quick Sizer * © Sizing Decision tree * Others Training opportunities FAQsStandard Sizing Methods and Tools Initial Calculation Method Questionnaire, without formulas ah & For structured questions TShirt Sizing Simple algorithms with UV many assumptions a Quick Sizer ‘Supports user: ah “ based and throughput-based Formulas sizing Simple or more XW =D +025 complex EE secimensonExampl Characteristics © Struotured sizing questionnaires = Iputfor ~ Greentield sizing = GoingLive Check = Hardware vendor contact list Facts and Figures * Available onne since 1996 « New Special Quick Sizer version for SAP S/4HANA Cloud «= HANA Quick Sizer version avaliable since 09/2014 + Froe of charge + As of 2016: avg 35.000 now projects per year Scope = SAP Key applications ~ SAP SiaHANA — HANA Standalone = SAP BW/AHANA = ete = Sizing by users andlor by throughput Quick Sizer, SAP’s Online Sizing ToolExample: Greenfield Sizing with Quick Sizer 7X7) - SomesAgenda Sizing SAP HANASAP HANA Customer Interested in EL Cesta DES LY Sizing Type acm PINE elite oie) rail) ROE Serer eeu rau) Irae ier Greenfield Brownfield (system Sizing Verification Definition Anew SAP conversion) After the system runs on application, which did ‘The SAP application SAP HANA, check not exist before exists on anyDB, whether the capacity anyOS, maybe ina estimation was right backlevel releaseSAP HANA Sizing ee um ec) ois uey DOUG) ee Unc RCO Cee} Ura} Use SAP HANA Quick Sizer Use Migration Reports/ Procedure (ow. sap.comsizing) (Notes: 1872170, 1783946, 2206200) Find deployment options: Hane Hodwere Brecon Connect with hardware vendor and check for configuration Link D>Greenfield SizingGreenfield Sizing New SAP HANA system (Greenfield Sizing) Use Quick Sizer RP Weny S/4HANA Cloud version Sere aa LULA Pr Methodology and sizing result —_ _ + Structured questionnaires for key ‘SAP applications * Overview about architecture and + Request MAXAttention Service or functionalities for selected business + Sizing results given in SAPS (CPU), Sizing Service from Consulting 8 (omary dno dak) and ask YO scenarios + Sizing results given as T-Shirt categories in SAPS (CPU) and GB * Qyonal: amon or poraistant (Memory & disk) jemory (NVRAIGreenfield Sizing for SAP S/4HANA Quick Sizer eerenacd Dees ene een UT nd in the Classic QS, e.g., the think times of the different user types (low, medium, high) are the same. Ea ae aekS MiceDemo \< Quick SizerNew Quick Sizer eye LAU act}Data Aging Data aging is a business data management concept for reducing the memory footprint in SAP HANA = Only operationally relevant (“hot"/current) data is loaded into main memory of SAP HANA = Other (‘cold’/historical) data remains primarily stored on disk, not affecting hot data performance, yet cold data remains accessible via SQL on request -3@ ets is =a eS]HANA Quick Sizer News Data Aging in 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 the aging column (residence time in memory) is empty and highlighted in blue. > Pe = Introduction of ‘What if analysis for the retention times (diskimemory)’Example What-If Analysis Data Aging Option 1: HANA Memory Result ~ 4.2TB for S/4HANA Server (24-month residence time in memory) st nce nt in “in tm a (fam) if Option 2: HANA Memory Result - 8.9TB for S/4HANA Server (no data aging) “nt anc an ne Fs ‘onan enn na | A irom om ieHANA Quick Sizer News 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 /O requirements with the SAP HANA Quick Sizer is now possible. pm) (a ereeescn a IB 0HANA Quick Sizer News Sizing SAP S/4HANA Embedded Analytics, The goal of sizing for Sizing SAP S/4HANA Embedded Analytics is: = To determine how many CPU coresithreads and memory are required for the processing of target number of parallel queries (without index support) And at the same time achieving the average target response time = With the HANA Quick Sizer, you can conduct a sizing for analytical apps nowHANA Quick Sizer News Sizing SAP S/4HANA Embedded Analytics The S/4HANA Embedded Analytics sizing has been implemented in the HANA Quick Sizer If the input of the involved sizing (e.g. Business area: Sales & Service) for embedded analytics is too big, no sizing result will be calculated. The following message appears to execute at least one of the following actions 1. Review and/or reduce the Concurrent Users sizing(s) of questionnaire 'X (e.g. Sales & Service)’ 2. Delete sizing(s) on questionnaire 'SAP S/4HANA Embedded Analytics’ for questionnaire 'X 8. Ifyou consider your input numbers as appropriate then please contact SAP (CSS component: XX-SER- SAPSMP-ST)HANA Quick Sizer News 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 —HANA-servers with Intel Cascade Lake CPUs ‘Trvouoout: Rests for Sotware Components cree My st ay ene a | sismen use stem uaea—_iean_ ses Calculation: Persistent Memory: Amount of memory required for the column store data DRAM: Total HANA Memory — Persistent MemoryHow to Size SAP S/4HANA Cloud?Sizing SAP S/4HANA Cloud Quick Sizer in Since June 2018, there is a new Quick Sizer for SAP S/4HANA ee Cloud available arene angela The tool can be used for S/4HANA Cloud greenfield sizings ence reeeee Main Characteristics of the Cloud Quick Sizer vrs = Simplified UI "SAP SUMAN Clo Logon = Streamlined Input Navigation Tree (scope items) ceca ea = Documentation in the SAP Help Portal 19 Aeteame Hom non SAE sens = External usage: Only two sizing KPI's (HANA RAM for Business data & Frontend Network Load) = Internal Usage: The two new KPIs (HANA RAM for Business data & Frontend Network Load) + CPU, disk space & Disk /O. oud = Sizing of API callsMigration SizingMigration Sizing Part 1/2 TT Ue eS CU) Doe CRC RGA LL SAP S/4HANA 1872170 1793345 Methodology and result + Sizing report (note 1872170) which runs on the ./egacy" (any D8, anyOS) ABAP system to determine the required HANA RAM and disk (on the new HANA-based soluvon + Potential areas for housekeeping, cleanup and archiving + Report ‘SDF/HDB_SIZING (Modification 77) contains enhancement for persistent memory sizing + CPU sizing: Willbe included inthe sizing report (type ful in transaction box). Recommendation: Double-check result with method as. described in SAP Note 1793345 SAP BW/4HANA 2296290 Methodology and result + Sizing report (note 229690) which runs on the source BV |ABAP system to determine the required HANA RAM and disk. + Potential areas for housekeeping, cleanup and archiving + In addition, a HANA CPU requirement assessmentis included + Persistent Memory sizing will be available soon Back 19 Overview D>Sizing Report for SAP S/4HANA Report /SDF/HDB_SIZING = Described in SAP Note 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 Fl, 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 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 itis 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 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 The sizing report /SDF/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!Migration Sizing Part 2/2 eu NCU to SAP HANA anneal Sean Renee ne ee) Se eee DCC ROE aL HANA native Fowler) SIE Arne) SAP S/4HANA pS Re) Back Ovewiew D>Sizing Verification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 1969700 ETNA EAC) 1872170 PAC 2296290 1698281 Back o Overview D>Deployment Options Virtualization — (HITACHI gern @redhat wKVM 4 Huawei Infrastructure as a Service (laaS) — Certified and Supported SAP HANA Directory vmware gt amazon ME Windows Azure QW Huawer Be Biuemix” ©) Google Cioud Platform Physical server - Certified and Supported SAP HANA Directory Corttied Cortted —_certiiea Appliances Enterprise laa Storage PlatformsAgenda Wrap-up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 AP. 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 1698281 - Assess the memory consumption of a SAP HANA System = SAP Note 1514966 ~ SAP HANA: Sizing SAP In-Memory Database HANA Quick Sizer (for greenfield sizing) Youtube Video D>Key Points to Take Home ee? a * Sizing means translating business requirements into hardware requirements = The success of the sizing exercise almost entirely depends on the quality of the data * Sizing involves very different people and teams within an organization = Expert sizing is recommended for custom development = The HANA sizing approach is different from the sizing of traditional databases * Sizing is not configuration * Greenfield sizings for HANA should be done with the HANA Quick Sizer and migration sizing of an existing NetWeaver-based system to SAP HANA should be done with the corresponding migration reportsThank you. Contact information’ Sebastian Schmitt SAP SE Product Management Coll: +49 151 18874932Folow us e000 wu sap.comeontaetsa peesesr nw SY