BI104-BI Accelator-QA.pdf

8/11/2019 BI104-BI Accelator-QA.pdf

1/41


2/41

Contributing Speaker

Tanuj Gupta Associate Support Architect, SAP Labs India

SAP AG 2007, SAP TechEd 07 / BI104 / 2


3/41

Learning Objectives

As a result of this workshop, you will be able to:

understand the architecture of SAP NetWeaver BI Accelerator

understand the new query runtime statistics in BI 7.0.

analysis of the SAP NetWeaver BI Accelerator query runtime



4/41

verv ew

Quer Runtime Statistics

BI Accelerator Query Runtime

BI Accelerator Transactions


5/41

SAP NetWeaver BI Accelerator: Vision

BI Accelerator for high performance BI

Performance speedup factor between 10 and 100 (compared to DB)

Without changing the BI user experience (transparent to users)Pre-requisite: SAP NetWeaver 7.0 BI

Queries Queries

SAP NetWeaver Business

IntelligenceBI Accelerator

Database

X



6/41

SAP NetWeaver BI Accelerator: Architecture

BusinessExplorer

Any Tool

BI Analytic

joins and aggregates in run time

Engine Query &Response

indexes loaded

InfoCubesIndexing

Data Acquis ition Any

Source creates and storesindexes for InfoCubes

SAP NetWeaver BI SAP NetWeaver BI Accelerator



7/41

Criteria for BI Query Acceleration

Query processing time comprises 3 componentsDatabase access, calculations (OLAP), client rendering

a resses e a a ase access mes

No Acceleration for uer es a are a rea y as w o aggrega es

Queries with high OLAP time

-

Complex authorization checksTransferred amount of data > 500,000 (rough indicator)

Acceleration for

Ad-hoc analysis/unpredictable query patterns

High database time

Big ratio DBSEL/DBTRANS


Queries that routinely need lots of aggregates


8/41

verv ew





9/41

New Query Statistics

Split ting the OLAP statistics into a FE/OLAP and aDataManager part.

. Many different events (FE/OLAP) vs. small number of events (DM)

Queries that are already fast w/o aggregatesIntroducing statistic detail levels on query (not just InfoProvider)Queries with high OLAP time

extensions) Long front-end events

Distributin the statistic information over several tables



10/41

Analysis of Query Runtime Statistics

In the Query Monitor (transaction RSRT), detailed query runtime statisticscan be displayed.



11/41

Event-IDs

Event-IDs:Definition in RSDDSTATEVENTSCommon concept used in query runtime, planning and warehousemanagement statistics

Most important Event-IDs:EVENT-ID / EVENT-RANGE Descri tion

2500 2530 OLAP Cache usage3000 3999 OLAP processing & calculation

4300 4600 Authorization checks

9000 Data Manager

12600 14600 Web application

15000 15100 BEx 7.x frontend

19900 19999 BEx 3.x frontend

40000 40100 MDX

50000 50010 Integrated planning



12/41


13/41

Query Runtime Overview



14/41

RSDDSTAT_OLAP: Details (I)

Used frontend Overall runtime (per step)

Administrative Info


Execution start time

S S A O A il ( )


15/41

RSDDSTAT_OLAP: Details (II)

Counter RuntimeEvent-IDs


2 keyfigure types


16/41


17/41

Data Manager details in RSDDSTAT DM (II)


18/41

Data Manager details in RSDDSTAT_DM (II)

Aggregate used ?

Fact tabletype

BasisInfoProvider

Database DBSEL &DM prepare



19/41


20/41

verv ew






21/41





22/41





23/41





24/41

cce e ato Que y u t e




25/41

Q y




26/41

Q y




27/41

SAP NetWeaver BI TREX ABAP

RFCServer

TREX Index Server Gateway

TREXClient

ABAP_RFC_TIME

RFC_SERVER_TIME

TREX_CLIENT_TIME

TREX_KERNEL_TIME



28/41

verv ew




BI Accelerator Monitor - Summary (RSDDBIAMON2)


29/41

Summary tab featuresan alert status icon

Click icon to see detailsbelow or right-click online and choose Details

BI accelerator monitor offering all themain administration tools you need


RSDDBIAMON2 Check Load Distribution


30/41

CPU per Proc. indicates single CPU utilization / per Index server / blade

Memory Process indicates memory utilzation / Index server / blade

Total Memory is the total memory utilzation / bladeIf load is not evenly distributed, either re-org (re-dist ibute) the BIA indexacross the blades or re-index the InfoCube


BI Accelerator Monitor - Go To 1


31/41


BI Accelerator Monitor - Go To 2


32/41



33/41

TREX Administration Tool


34/41

TREX Admin Tool is a stand-alone program that you can use to

administer TREX independently of the application to which i t isconnected.

The application that is connected to TREX normally provides its own

administ ration tools for TREX too. You should use the administ rationtools provided by the application where possible. Only use the TREXadmin tool for the functions that are not available in the administrationtools of the application.


Transaction TREXADMIN - 1


35/41



36/41

Table RSADMIN QUERY_MAX_WP_DIAG


37/41

QUERY_MAX_WP_DIAG is a parameter in table RSADMIN.

query (non-BIA and BIA) could potentially use.The BI system reserves 5 DIA (dialog) work processes open anduses the formula: (MIN(# InfoProviders, QUERY_MAX_WP_DIAG)+ 5) to determine whether or not to parallelize query execution.Default value = 6. Hence there NEEDS to be atleast 11 DIA workprocesses free in order to execute query in parallel.For additional information, refer to SAP Note 895530.


Summary


38/41

SAP NetWeaver BI Accelerator improves Query databasetime

New Query Runtime statistics are flexible and available forfurther extensions

SAP NetWeaver BI Accelerator Query Runtime statist ics canbe viewed using the table RSDDSTATTREXSERV

Transactions RSDDBIAMON2 and TREXADMIN can be usedto monitor the SAP NetWeaver BI Accelerator.


Further Information


39/41

SAP Public Web: . . .

Business Process Expert (BPX) Community: www.bpx.sap.com

http://www.sap.com/education/



40/41


41/41

Please complete your session evaluation.

Be courteous deposit your trash,and do not take the handouts for the following session.

Th k Yhank You


Documents

BI104-BI Accelator-QA.pdf