Sap Bw on Hana Sizing v1 7

SAP & SAP Customer Internal

SAP BW on HANA (Orange)

Sizing Guideline Version 1.7 – December 2014

SAP & SAP Customer Internal

© 2012 SAP AG. All rights reserved. 2 SAP & SAP Customer Internal

DISCLAIMER

Sizing recommendations apply for certified hardware only. Please contact

hardware vendor for suitable hardware configuration.

Note that HANA is constantly being optimized. This might have impact on

sizing recommendations, which will be reflected in this document. Therefore,

check for the latest version of this document and the note.

Note that the sizing guideline in this document refers to new installations of

SAP BW on HANA only. Additional applications running on top of HANA are

not covered in this document. Please refer to application specific sizing

guidelines for details in that case.

Also note that for sizing a system after migration from another database

platform SAP note 1736976 applies. Do not use this sizing guideline for

system migration!


SAP BW on HANA Sizing Elements

SAP BW on HANA sizing consists of

Memory sizing for column store data

Memory sizing for row store data

Memory sizing for objects created during runtime

(data load and query execution)

Disk Sizing


SAP BW on HANA Sizing: Summary

1. RAM

2. Disk

RAM = (Source data footprint – 60GB) * 2 / 4 * c1) + 110 GB or

RAM = ( colstore tables footprint * 2 / 4 +

rowstore tables footprint / 1.0 ) * c1) + 50 GB

DISKlog = 0.5 * RAM, max. 512GB

DISKpersistence = 1 * RAM 2)

1) c = source database specific compression factor (where applicable – see page 8) 2) Additional disk space required for backups, exports, shared volumes - see pp. 9f


Memory Sizing: Column Store Data

• Memory requirements for column store data is derived from the database footprint

of the corresponding tables of the source database system

• The overall database footprint in source system must be determined using

database specific catalog information (e.g. in Oracle: dba_segments; in DB2:

syscat.tables).

• It is assumed that part of database tables will be stored in row store (all tables that

are NOT generated by BW). In cleansed BW system this is usually about 60 GB

worth of data. However, with large customer data tables, this size can grow

significantly. Note 1637145 contains scripts that identify row store and column

store tables and their cumulated sizes.

• Average compression factor database table size : column store size = 4 : 1

• Note that this compression factor refers to uncompressed database tables, and

space for database indexes is to be excluded.


Memory Sizing: Row Store Data and Caches

• A cleansed BW system usually has about 60 GB of database tables that will be

stored in row store (data dictionary, housekeeping tables, etc.).

• Average compression factor database table size : row store size = 1.0 : 1

A fixed amount of 60 GB for row store data for BW is assumed.

• HANA uses additional caches to accelerate I/O to persistence layer and for other

purposes. These caches can grow but will shrink if memory is needed to store

data. However, a minimum amount of cache memory of 40 GB has been

identified.

• Additional HANA components (statistics server, name server) require 10 GB of

memory.

• Sum of memory not covered by column store: 110 GB


Memory Sizing: Runtime Objects

Additional memory required for objects that are created dynamically

when loading new data

when executing queries

We recommend to reserve as much memory for dynamic objects as for static

objects in column store:

So the total RAM is

RAMdynamic = RAMstatic

RAM = (Source data footprint – 60GB) * 2 / 4 * c1) + 110 GB or


rowstore tables footprint / 1.0 ) * c1) + 50 GB

1) c = source database specific compression factor (where applicable – see page 8)


Memory Sizing: Remarks

• Compression in source database

The sizing scripts attached to note 1637145 do NOT take into account reduced sizes of the

source data due to database intrinsic compression – except the ones for the IBM DB2

family (DB2, DB4, DB6), where compression factors for each table are contained in the

database dictionary. These scripts deliver correct results also for a compressed database.

• If the source database other than from the DB2 family is compressed, you have to adjust

the results of the scripts by a database compression factor. Your DB administrator should

be able to help obtaining this factor.

• Unicode vs. Non-unicode database

Migration to HANA is only possible from a unicode system, so the sizing scripts assume a

unicode enabled source database. If the scripts are executed on a non-unicode database,

we recommend to add a small uplift (since BW operates mainly on numeric data, an uplift

of no more than 10% to the script results should be enough).


Disk Sizing

Disk size for persistence layer:

Disk size for log files / operational disk space:

Note that this only covers disk requirements for the database files. As with

any database system, additional space must be reserved for

• Backup

• Exports

• Executables

We recommend reserving approximately another 2-3 times the RAM value for

these purposes.

DISKlog = 0.5 * RAM, max. 512GB

DISKpersistence = 1 * RAM

For details please refer to the HANA

Storage Requirements Whitepaper:

http://scn.sap.com/docs/DOC-60313


Disk Sizing - Details

Disk space is required to persistently store data that is kept in memory.

The space to be provided must be capable to hold:

• Data files (1x)

• Space for at least one process image in case of software failure (1x)

• Space for one data export (1x)

• Space for executables, system log files, etc. (1x)

The latter two components are essential to provide support. So a total of 4x

the size of the data in memory is required on disk.

Note that any backup data must NOT be stored in this space, but should

rather be moved to external storage media.


CPU Sizing

A large number of different non-tangible facts have significant impact on

HANA CPU sizing:

• Choice of front-end technology

e.g. SAP BusinessObjects Explorer vs. SAP AnalysisOffice

• Effects of different HANA engines, depending on query definitions

• etc.

A reliable user based CPU sizing for HANA is therefore not feasible.

Since memory is the dominating factor of a sizing exercise, there is a fixed

ratio of RAM and CPU in all hardware configurations certified for BW on

HANA (16 GB / core for 8-core CPUs, 12.8 GB / core for 10-core CPUs,

17 GB / core for 15-core CPUs)


Example

Extract from sizing script output: Fill Table HANA_ROWSTORE ...

Fill Table HANA_COLSTORE ...

Get Total Sizes for RowStore and ColumnStore Tables (without Aggregates) ...

-----------------------------------------------------------------------------------------

-- Relevant Sizing Information

-- HINT: Aggregates were removed while calculating Size for ColumnStore

-----------------------------------------------------------------------------------------

RowStore Tables [GB] ColumnStore Tables [GB] Total Size [GB]

-------------------- ----------------------- ---------------

49.56 672.35 701.91

Table footprint of source database: 50 GB row store + 672 GB column store

Assumption: source DB compressed by factor 1.8


rowstore tables footprint) / 1.5 ) * DB compression + 50 GB

= (672 GB * 2 / 4 + 50 GB / 1.0) * 1.8 + 50 GB = 745 GB

Diskpersistence = 745 GB * 4 = 2,980 GB

Disklog = 512 GB


Disadvantages of DB specific scripts:

• Extra handling of source DB specific compression factor

• Special privileges required to execute scripts (OS access, DB admin privileges)

• No semantic / application specific knowledge in script logic (e.g. table types with distinct

compression factors for InfoCubes, DSOs, etc., concept of non-active data)

• Limited precision due to lacking reflection of HANA memory optimization concepts

Scripts are good for first rough sizing estimate, but:

Enhanced BW on HANA Sizing: ABAP Report

For a more sophisticated sizing approach, we strongly recommend

using the ABAP based BW Sizing report described in SAP note 1736976

© 2012 SAP AG. All rights reserved. 16

© 2012 SAP AG. Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind,

zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche

schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation

enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte

können Softwarekomponenten auch anderer Softwarehersteller enthalten.

Microsoft, Windows, Excel, Outlook, und PowerPoint sind eingetragene Marken

der Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5,

System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries,

zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390

Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6,

POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,

BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF,

Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere,

Netfinity, Tivoli und Informix sind Marken oder eingetragene Marken der IBM

Corporation.

Linux ist eine eingetragene Marke von Linus Torvalds in den USA und anderen

Ländern.

Adobe, das Adobe-Logo, Acrobat, PostScript und Reader sind Marken oder

eingetragene Marken von Adobe Systems Incorporated in den USA und/oder

anderen Ländern.

Oracle und Java sind eingetragene Marken von Oracle und/oder ihrer

Tochtergesellschaften.

UNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame und

MultiWin sind Marken oder eingetragene Marken von Citrix Systems, Inc.

HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des

W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects

Explorer, StreamWork und weitere im Text erwähnte SAP-Produkte und -

Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene

Marken der SAP AG in Deutschland und anderen Ländern.

Business Objects und das Business-Objects-Logo, BusinessObjects, Crystal

Reports, Crystal Decisions, Web Intelligence, Xcelsius und andere im Text

erwähnte Business-Objects-Produkte und Dienstleistungen sowie die

entsprechenden Logos sind Marken oder eingetragene Marken der Business

Objects Software Ltd. Business Objects ist ein Unternehmen der SAP AG.

Sybase und Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere und

weitere im Text erwähnte Sybase-Produkte und -Dienstleistungen sowie die

entsprechenden Logos sind Marken oder eingetragene Marken der Sybase Inc.

Sybase ist ein Unternehmen der SAP AG.

Alle anderen Namen von Produkten und Dienstleistungen sind Marken der

jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu

Informationszwecken. Produkte können länderspezifische Unterschiede

aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe

und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem

Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher

Genehmigung durch SAP AG gestattet.

Documents

Sap Bw on Hana Sizing v1 7