For analyzing a performance issue in BEx Analyzer 7x it is necessary to create a Statistics Workbook first of all.With the Statistics Workbook you can identify the time consuming events while query/workbook processing in BEx Analyzer 7x.This page describes how the Statistics Workbook can be recorded and you can find information about Frontend related statistic events and their optimization. Please also review wikipage Optimizing BEx Analyzer 7x Performance - NEW.
A - Create a Statistics Workbook
The creation of a Statistics Workbook is explained in note 1083462. Please use following steps:
- Open the BEx Analyzer 7x via Windows Start Menu.
In the Gobal Settings dialog go to tab Statistic and activate the checkbox Collect Statistics:
- Close the BEx Analyzer and restart it.
- Now reproduce the performance issue. For SAP support please write down following details:
3.1. Workbook ID from the analyzed workbook (see Find the Workbook ID)
3.2. Create a global variable variant of the used variable selection and write down the technical name of this variant. With this variant, we make sure to use the same variable selection.
3.3. Provide the exact navigation steps which were done while recording of the Statistics Workbook.
3.4. Add the '(Nav.) Step Counter' (1st column in Statistics Workbook) to the reproducing steps list.
3.5. Stop recording by removing the flag Collect Statistics in the Gobal Settings dialog on tab Statistic, and click ok to close the Global Settings.
3.6. Access Global Settings again, on tab Statistic press button Display Statistics to display the Statistics Workbook.
- Please add the Statistic Object Name to the rows with following steps:
- See following Example Statistics Workbook:
B - The heading columns of the Statistics Workbook
(Nav.) Step Counter
Statistic Object Name
Counter for Statistic Event calls
The step ID is counted up for each navigation step. For communication with SAP please write down what you have done in each step. If the workbook has more than one dataprovider then for processing each dataprovider one step is created.
This is the name of the event.
Here the technical name of the query, the key of the workbook or the ID of BEx Item are shown.
This is the runtime of event given in seconds.
For certin events you will find a value which indicates a size.
C - Frontend related events in detail
In the Online Documentation you can find a general Overview of Statistics Events (table RSDDSTATEVENTS).
The number indicates the transfered bytes for one step.
This is the time for transfering the workbook from backend to temp. folder of client.
This event measures the time taken to generate the constructor of a workbook.
This is a collective event for all parts that are not explicitly assigned to an event. The parts that are not assigned to an event are not belonging to the backend or frontend. This time is spend somewhere in between, durring the frontend backend communication. In most of the cases this is the network load (WAN). Especially if your Citrix Servers are located far from the application servers and the network load is high.
This is the time which belongs to data transfer in the landscape after leaving the BW server and before reaching the frontend tool, it includes complete time for network-traffic and occurs for every data transfer between BW Server and frontend. To improve the performance in the frontend/backend communication you should apply following notes:
How many cells reads the database.
Number of Excel Cell
This is the amount of data which is sent across the network.
This event measures the time taken to process a Dialog (including the waiting time): selector dialog, open save dialog and variable screen.
Number of Blocks
Number of Blocks
Number of Symbols
Number of Symbols
It is simply preparing the sheets for a clean rendering.
This is the Excel formatting time for rendering the BEx items. In column Statistic Object Name you can identify which BEx Item consumes the time.
This is the time which is spent after rendering the design items. The time is mainly required by Excel for applying the formatting, drawing the graphs, formula calculation, exit macros (Workbook-Settings > TAB Exists > Run Macro On Refresh).
Wait Time, User
It is the time when the application was waiting for user action.
D - OLAP related events
These events are not are not relavnt for BEx Analyzer 7x. This runtime will be same in BEx Analyzer 3x, Tx RSRT or JAVA WEB. Please understand that the OLAP related events are not in focus of this wikipage, but you can find some short information about these events. Please also have a look at note 1681396
OLAP: Query Generation
This event measures the time that is needed to check the query definition and, if necessary, to generate the query
Authorization Check Selection
This event measures the time taken to carry out the OLAP authorization check.
Structure-/format-converting for frontend presentation. It can be optimized with help of compression & aggregates.
Total Number of Transported Records
Total Number of Read Records
OLAP: Data Selection
This event measures e.g. the time taken to sort the read data (from DM) according to structure element selections or restricted key figures. The calculation of virtual key figures is done here as well.
In this part of the coding many OLAP features are processed, e.g. exception aggregations are carried out, formulas are calculated, and the correct number of decimal places for the data cells is determined. The time can be optimized by using cache. The number indicates the number of cells.
OLAP: Read Texts
Texts are read to sort the data. This event measures the time taken to call the text read class
Link to this page: http://wiki.sdn.sap.com/wiki/x/QANdDw
KBA Bridge 2518355 - Optimizing BEx Analyzer 7x Performance - Wikipage