Vous êtes sur la page 1sur 31

SAP HANA on

IBM POWER Systems

Rahul Kulkarni
Power Systems Consultant
rahul_kulkarni@in.ibm.com

Agenda

SAP HANA
Current challenges in ERP environment (OLTP Vs OLAP)
What is SAP HANA?
SAP HANA Application Use Cases
Row Store Vs Column store

HANA on Power (HoP)


SAP and IBM Relationship
HoP Performance Benefits
HoP RAS Benefits
Supported Application Use Cases
HA/DR options
Current status of HANA on Power

Introduction to HANA

OLTP vs OLAP
Modern ERP systems are challenged by mixed workloads, including OLAP--style queries.
For example:
OLTP--style: create sales order, invoice, accounting documents, display customer
master data or sales order
OLAP--style: sales figures aggregated and grouped by regions, different timeframes and
products
But: Todays data management systems are optimized either for daily transactional or
analytical workloads storing their data along rows or columns
Drawbacks of the OLTP and OLAP separation:
OLAP system does not have the latest data
OLAP system does only have a predefined subset of the data
Cost--intensive ETL process has to synch both systems
There is a lot of redundancy
Different data schemas introduce complexity for applications that combine sources
4

OLTP vs OLAP
Enterprise Data Characteristics:
Many columns are not used even once
Many columns have a low cardinality of values
NULL values/default values are dominant
Sparse distribution facilitates high compression
Standard enterprise software data is sparse and wide

SAP HANA Vision:


Combine OLTP and OLAP data using modern hardware and database systems to
create a single source of truth, enable real-time analytics and simplify applications and
database structures.
Additionally:
Extraction, Transformation and Loading (ETL) processes and pre-computed aggregates
and materialized views become obsolete.
5

In Memory Computing: Re-think Paradigms

In-Memory Computing Imperative:

Avoid movement of detailed data


Calculate first, then move results

HANA: More than just a database a platform


From:

One DB per application

Point-to-point integration (e.g. ETL)

Long running queries, e.g. in batch mode

To:

One DB per landscape

No integration necessary

Real time execution

Vision, not reality yet

SAP HANA Application Use Cases

Traditional Row-Oriented Storage

Rows are stored sequentially


Provides best performance when most queries are for multiple columns of a single row
(OLTP applications)
Indexes on high-cardinality columns make accessing a single row very fast but dont help
on analytical queries scanning many rows:
Exa. Whats the average age of males?
If the tables are large (~ 100GBs or TBs) you would have to:
Read the whole table and/or
Build complex composite indexes
9

Column-Oriented Storage

Data in columnar model is kept in columns


Since data in a single column is almost always homogeneous it's frequently compressed which often
provides for dramatic reduction in memory consumption.
Aggregate functions are very fast on columnar data model since the entire column can be fetched very
quickly and effectively indexed.
Inserts, updates and row functions, however, are significantly slower than their row-based counterparts
as a trade-off of columnar approach (inserting a row leads to multiple columns inserts)
Assistance provided by Delta Merge Process
10

SAP HANA Delta-Merge Process

A column store table is comprised of two index types for each column, a Main index
and a Delta index.
The Delta storage is optimized for write operations and the Main storage is optimized
in terms of read performance.
The use of the Delta tables addresses the performance issues of loading directly to
compressed columns.
This is a very CPU/Memory intensive task (!!!)
11

HANA on Power (HoP)

http://www.ibm.com/solutions/sap/us/en/landing/pinnacle_awards.html?cm_sp=MTE27254

IBM wins SAP Pinnacle Award in 2015

For over 43 years, IBM and SAP have helped clients formulate and execute
winning strategies. Since the SAP Pinnacle Awards began in 2002, IBM has
won 31 awards more than any other SAP partner

IBM offers extensive strategy and business consulting, technical


implementation skills, and post-implementation support. And as a hardware
vendor with a financing arm, it can often bundle together innovative deals
and pricing arrangements for its clients.
.. Forrester Wave 13

SAP HANA
Now available on the first
Platform designed for data

IBM POWER8
14

SAP HANA on IBM POWER Systems

+
SAP HANA on Power is targeting enterprise customers requiring an SAP HANA-based
solution on IBM Power Systems servers
IBM intention is not to offer it as an appliance, but in a flexible form combining the
HANA license from SAP and IBM Power Systems servers, middleware and services.

15

HoP Benchmark Results

Per core performance on Power is close to 2X


compared to Intel
For details Refer SAP Benchmark site
http://global12.sap.com/solutions/benchmark/bweml-results.htm

All above listed servers used 1 TB main memory and test ran for 2,000,000,000 records

Comparisons to Intel Systems - Performance

Memory Speed

POWER8 Memory RAS features

Power Systems RAS vs x86 RAS


RAS Feature
Application/Partition RAS
Live Partition Mobility
Live Application Mobility
Partition Availability priority
System RAS
OS independent First Failure Data Capture
Memory Keys (including OS exploitation)
Processor RAS
Processor Instruction Retry
Alternate Processor Recovery
Dynamic Processor Deallocation
Dynamic Processor Sparing
Memory RAS
Chipkill
Survives Double Memory Failures
Selective Memory Mirroring
Redundant Memory
I/O RAS
Extended Error Handling
I/O Adapter Isolation (PI-Bus and TCEs)

POWER8

x86

Yes
Yes
Yes

Yes
Yes, support issues
No

Yes
Yes

EX MCA Recovery
No

Yes
Yes
Yes
Yes

No
No
No
No

Yes
Yes
Yes
Yes

Yes, some vendors


Yes, optional
No
Yes

Yes
Yes

No
No

HANA Appliance and TDI models on Intel


HANA Appliance
Fast Implementation
Support fully provided by SAP

Solution validation done by SAP and


partner
Preconfigured hardware set-up
Preinstalled software

TDI Tailored Datacenter Integration


More Flexibility
Save IT budget and existing investment

Installation needs to be done by


customer
Customer aligns with the hardware
partner on individual support mode

HANA on Power A TDI model

POWER8 hardware of your choice


POWER7+ for non-production environments
Operating System of your choice
SUSE Linux Enterprise Server 11 SP3 for IBM Power is currently supported, RHEL is
planned.
Storage and network of your choice
Should satisfy HANA KPI requirements
High Availability of your choice
HANA system replication is supported in first release, 3 rd party HA extensions are planned

Power servers comes with virtualization built into hypervisor.

Conceptual solution with HANA on Power

HWCCT Hardware configuration check tool


Customer in TDI environment need
to run HWCCT to determine if
system meets KPI requirements.
HWCCT checks for
Landscape validity
OS configuration validity
Consistency of landscape
based on reference
architecture
File system throughput/latency
Network throughput for multinode configurations
9.5 GBits for single stream
9.0 GBits for duplex stream

Disk IO performance requirement in TDI environment

Supported Use Cases and Scope


High Level Summary

Operating System
SUSE Linux Enterprise Server 11 SP3 for IBM Power (plus additional packages)
Hardware
Minimum IBM Power Server with POWER8 processor technology
Minimum IBM Power Server with POWER7+ processor technology (for non-production
environments)
Core to Memory Ratio
The initial core to memory ratio for SAP HANA on POWER is 32 GB per core
If the planned system size exceeds either 3 TB or does not fit into the ratio please contact
SAP
Use Cases
At the first release, only SAP Business Warehouse (BW) on SAP HANA is supported,
scale-up only
SAP HANA HA & DR: one active master host and one standby host in a failover scenario
SAP NetWeaver BW version 7.31 or higher

Supported Use Cases and Scope

SAP HANA, version for IBM Power Systems architecture Scope Description
Central SAP Release Note 213369 for SAP HANA on IBM Power Systems
SAP Note 2055470 HANA on POWER planning and installation specifics

SAP HANA on IBM Power Systems and IBM System Storage - Guides
Technical details about how to plan and deploy SAP HANA on IBM Power Systems SAP
external IBM Planning Guide on IBM Techdocs
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102502

LAN Connectivity Pattern for HoP Instance


For redundancy with dual-VIO setup plan these ports per VIO:

If dedicated I/O is used, plan for redundant I/O adapters per server
Dual-VIO requires access to a HMC. IVM is not supported

High Availability and Disaster Recovery Setup

Production site

DR site

SAP HANA on POWER Current Status

Ramp-Up period
Customer Test and
Evaluation phase

General
availability

November 2014 February 2015

Release to Customer
Ramp-Up Start
March 2015

Generally Available
from 21-Aug-2015

Summary

SAP HANA
Current challenges in ERP environment (OLTP Vs OLAP)
What is SAP HANA?
SAP HANA Application Use Cases
Row Store Vs Column store

HANA on Power (HoP)


SAP and IBM Relationship
HoP Performance Benefits
HoP RAS Benefits
Supported Application Use Cases
HA/DR options
Current status of HANA on Power

Thank You