bw performance tuning

Download BW Performance Tuning

Post on 22-Oct-2014

623 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

BW Performance TuningVersion 1.6 May 7, 2003

Dr. Thomas Becker Alexander PeterSAP AG

TargetsHow To Help YourselfOverview on most important performance issues Performance Tools in SAP Service Marketplace

Please do Measure the progress of your own performance tuningMeasure before tuning Tune the system according to the tips and via using provided tools Measure after tuning

Provide Feedback

SAP AG 2002, BW Performance Tuning, Alex Peter, 2

BW Architecture

SAP AG 2002, BW Performance Tuning, Alex Peter, 3

ContentsGeneral Settings and Checklist Modeling Query Performance Extraction / Data Load Performance Analysis Methods

SAP AG 2002, BW Performance Tuning, Alex Peter, 4

Performance GuidelinesGeneral Settings and Checklist Modeling Query Performance Extraction / Data Load Performance Analysis Methods

SAP AG 2002, BW Performance Tuning, Alex Peter, 5

Performance Tuning in BWPerformance TuningOLTP SystemsApplication Development and performance tuning separated Performance tuning by basis experts Database Application Performance Tuning

OLTP

BWPerformance Tuning as holistic process over application design and database configuration

BW

Database

Application Performance Tuning SAP AG 2002, BW Performance Tuning, Alex Peter, 6

General Performance Rules

Basic Rules for Performance Optimization:

Be economic: Eliminate all unnecessary processes Keep it small: Reduce the data volume to be processed Do it parallel: Deploy parallelism on all available levelsParallel processes are fully scalable SAP AG 2002, BW Performance Tuning, Alex Peter, 7

Checklist 1 Basis ParameterSAP Recommendations according to SAP note 192658 Also consider process settings: SAP BW does not need an UP2 process and at most 2 UPD processes

Database ParametersCheck of most important parameters via transaction RSRV database parameters (not available for all platforms) ORACLE DB parameter recommendations: SAP note 180605 Informix DB parameter recommendations: SAP note 181945 IBM DB2/UDB DB parameter recommendations: SAP notes 302429 (BW 2.x), 546262 (BW 3.x) IBM DB2/OS/390 parameter recommendations: SAP note 390016 IBM DB2/iSeries parameter recommendations: SAP notes 307077, 501572, 541508 SQL Server DB recommendations: SAP notes 327494, 28667

SAP AG 2002, BW Performance Tuning, Alex Peter, 8

Checklist 2 ORACLE-specific Database TuningORACLE 8.1.x-scripts for improved meta data access as described in SAP note 565075 Locally managed tablespaces: if you run BW 2.x, be sure that SAP notes 359835 and 387946 are applied. Be sure that your BW 3.x temporary tablespace is locally managed. Database statistics: SAP notes 351163 and 428212

Database PartitioningUse DB partitioning, especially for large InfoCube tables ORACLE, Informix and DB2/OS390 support range partitioning, DB2/UDB supports hash partitioning

SAP AG 2002, BW Performance Tuning, Alex Peter, 9

Checklist 3 Web Application Tuning in BW 3.xUse HTTP Compression to reduce network traffic: see SAP note 550669 Use Client (browser) caching of images to reduce unnecessary network traffic: see SAP note 561792

BW 3.0B SP9 / BW 3.1 Content SP3 or higherWe strongly recommend these support packages Internal measurements have proven an average improvement of over 40% (compared to 3.0B SP4) in Web Application Performance

SizingDecisive Factors: Number and Speed of CPUs, Main Memory, Disk Volume and Architecture (e.g. RAID), I/O-Controller Rough Sizing available in SAP Service Marketplace alias quicksizer In cooperation with hardware partner

SAP AG 2002, BW Performance Tuning, Alex Peter, 10

Checklist 4 Sound Data ModelThe Data Model is one of the most important issues

BW Reporting PerformanceAggregates Pre-calculated Web Templates OLAP Cache

Extraction / Data Load PerformanceRecommendations in SAP notes 130253 and 417307

SAP AG 2002, BW Performance Tuning, Alex Peter, 11

Performance Guidelines General Aspects 1 Database (or Physical) PartitioningDatabase tables are cut into smaller chunks (partitions) One logical database table Transparent for user Available for the following database management systemsRange Partitioning: ORACLE, Informix, IBM DB2/390 Hash Partitioning: IBM DB2/UDBYear / Month Customer Sales 2003/01 4711 10 2003/01 4712 15 2003/01 4713 20 2003/01 4714 23 2003/02 4711 44 2003/02 4713 32 2003/02 4714 17

Database Table(logical)

Database Partition

Database Partition

SAP AG 2002, BW Performance Tuning, Alex Peter, 12

Performance Guidelines General Aspects 2 Database (or Physical) PartitioningBenefitsParallel accesses to partitions Read smaller sets of data Fast Deletion of partitions (DROP PARTITION instead DELETE FROM WHERE)

Automatically Partitioned Database Tables (for Range Partitioning)InfoCube F-Fact table: partitioned by request PSA table: partitioned by request ODS Change Log: similar to PSA table

User Defined Partitioning Criteria (for Range Partitioning)InfoCube E-Fact table Partition Criteria: Time characteristics like month or fiscal period Note: Both fact tables are extended by the SID of the chosen time characteristic

SAP AG 2002, BW Performance Tuning, Alex Peter, 13

Performance Guidelines General Aspects 3 Database (or Physical) PartitioningQuery Access (Partition Pruning)Package

Example: Month = August 2003Package 2 Package 5 Package 7

F table has to be read, too F

month Master Data

Time DimensionJan - Mar Apr - Jun Jul - Sep Oct - Dec

E

Month Customer Sales Aug 03 4711 15 Aug 03 4712 66

Fact Table Apply Restrictions to Dimensions SAP AG 2002, BW Performance Tuning, Alex Peter, 14

Discard irrelevant partitions

Apply Restriction to fact table

Performance Guidelines General Aspects 4 Distribution of workloadApplication Server groups / Load BalancingLogon load balancing (via group login): this allows you to distribute the workload of multiple query/administration users across several application servers Distribution of web users across application servers can be configured in the BEx service in SICF ODS Object Data Activation is definable for specific server groups (BW 3.x) Process Chains can be processed on specified server groups (BW 3.x) Extraction in the mySAP source system can be processed on specified server groups: RFC destination in BW to source system must be defined accordingly (transaction SM59) Data load in BW can be processed on specified server groups: RFC destination in source system to BW must be defined accordingly (transaction SM59) Data staging via XML over HTTP/SOAP can be processed on specified server groups (BW 3.x)

Operation modesDifferent modes for mainly query processing (many dialogue jobs) and data load (several batch jobs) SAP AG 2002, BW Performance Tuning, Alex Peter, 15

Performance Guidelines General Aspects 5 Other AspectsReorganization of Log TablesSLG2 (SAP note 195157) EDI40 (SAP note 179046) RSDDSTAT-tables

Check for unnecessary traces and logs that impact system performanceAuthorization log (RSSMTRACE) User Trace (RSRTRACE) SQL Trace (ST05) ABAP Trace (SE30) Statistics Trace

SAP AG 2002, BW Performance Tuning, Alex Peter, 16

Performance Guidelines General Aspects 6 Other AspectsArchiving (as of BW 3.x)Reduction of number of records in InfoCube fact tables / ODS object tables

InfoCubes

Optical Storage system

ArchiveFiles ODS object

HSM System

ArchiveFiles

Storagesystem

BW Functionality with ADK

3rd party products

SAP AG 2002, BW Performance Tuning, Alex Peter, 17

Performance GuidelinesGeneral Settings and Checklist Modeling Query Performance Extraction / Data Load Performance Analysis Methods

SAP AG 2002, BW Performance Tuning, Alex Peter, 18

ChecklistDesign of Operational Store, Data Warehouse Layer and Multidimensional Model Dimensions of InfoCubes Logical (MultiProvider) Partitioning Time-Dependent Master Data Non-Cumulative Key Figures

SAP AG 2002, BW Performance Tuning, Alex Peter, 19

Operational Data Store and Data Warehouse Layer

Data WarehouseNon volatile Granular Integrated Historical foundation Built with ODS ObjectsODS Object SAP AG 2002, BW Performance Tuning, Alex Peter, 20

Operational Data StoreOperational Reporting Near Real-Time / Volatile Granular Built with ODS Objects

Multidimensional ModelsMultidimensional analysis Aggregated view Integrated Built with InfoCubes

ODS Object

InfoCubesSAP-Extended Star SchemaONE Normalization of Dimensions Master Data is shared, not part of the InfoCubeMaster Master Data Data Dimension Dimension Dimension DimensionDimension ID

Master Master Data DataSurrogate Key

Fact Table Fact Table

Dimension Dimension Master Master Data Data SAP AG 2002, BW Performance Tuning, Alex Peter, 21

Dimension Dimension Master Master Data Data

InfoCubesMaster DataHierarchies Attributes Texts (Multi-Language Support)Master Master SID Table SID Table Data Data Dimension Dimension

Hierarchies

Fact Table Fact Table

AttributesCustomer Street Account

TextsPlant UK Plant Germany Plant Australia

SAP AG 2002, BW Performance Tuning, Alex Peter, 22

Data Modeling Line Item Dimensions 1 Line Item DimensionsDirect Link from InfoCube Fact Table to Master Data SID Table without dimension table Only one characteristic is possible in a line item dimension Recommended for large dimensions (e.g. invoice number, order number, but also reasonable for large material or customer dimensions)

SID

Dimensi