Académique Documents
Professionnel Documents
Culture Documents
Is this your user community? How can you avoid this BEFORE it happens?
3
The Key to BI Success Performance is more important than price for the senior management.
1,873 managers and business leaders were asked what factor was most important for their BI application.
Even in a recession, the key to BI success was functionality, ease of use, integration and Performance.
Price, standards, product reputation and architecture was of lesser importance.
Source: Business Research Center Survey
BW InfoCubes Observations
Infocubes Available options Jobcost history cube Options sold MH AP line item cube MH AR line item cube MH general ledger cube Cost cube MH property master (LOT) cube Purchasing item data Inventory cube PS controlling MH PS dates MH PS controlling and dates cube Earnest money estimation cube MHSD overview SD commissions cube Characteristics Navigational Time char- Hierarchies Dimensions Key figures attributes acteristics 20 4 4 2 9 4 57 0 1 0 12 1 23 19 4 1 11 14 52 13 4 3 10 15 29 0 4 1 8 20 30 2 5 6 8 9 14 0 3 2 8 2 24 2 4 1 11 7 13 10 5 3 11 15 33 4 2 3 9 23 44 37 5 10 12 35 25 19 5 4 8 17 34 48 3 5 9 30 40 24 5 7 13 16 49 28 5 7 13 27 51 22 4 4 10 21 Record Complexity length Moderate Moderate High High Low Low High High Low Low Low Low Low Low Low Low Low Low Low Low High Moderate Moderate Low High Low Moderate High High High High 8 High
Characteristics
BW InfoCubes Observations
Infocubes Available options Jobcost history cube Options sold MH AP line item cube MH AR line item cube MH general ledger cube Cost cube MH property master (LOT) cube Purchasing item data Inventory cube PS controlling MH PS dates MH PS controlling and dates cube Earnest money estimation cube MHSD overview SD commissions cube Characteristics Navigational Time char- Hierarchies Dimensions Key figures Record Complexity attributes acteristics length 20 4 4 2 9 4 Moderate Moderate High 57 0 1 0 12 1 High 23 19 4 1 11 14 Low Low 52 13 4 3 10 15 High High Low 29 0 4 1 8 20 Low Low 30 2 5 6 8 9 Low Low 14 0 3 2 8 2 Low 24 2 4 1 11 7 Low Low 13 10 5 3 11 15 Low Low Low 33 4 2 3 9 23 Low High 44 37 5 10 12 35 Moderate Moderate 25 19 5 4 8 17 Low High 34 48 3 5 9 30 Low 40 24 5 7 13 16 Moderate High High 49 28 5 7 13 27 High High 51 22 4 4 10 21 High
In general, a common BW configuration contains a set of characteristics that are used for analysis purposes. The number of these characteristics varies from implementation to implementations. Typically configurations ranges from 1 to 40y characteristics. The design depends largely on the requirements of the business, but there are some technical tradeoffs in load times when adding a very high number of characteristics. This is particularly true when these contains large text fields that are loaded at a high frequency and at a high number of records.
10
Key figures While no limitations are imposed by BW in terms of number of key figures (measures), typical implementations contains 1 to 20 of these. While a higher number of these may be required, there a are significant tradeoffs of load performance when a high number records are loaded (these are loaded with each transaction).
11
Record Length
Record length In general, as the record length of an InfoSource increases, more data may be populated to the InfoCube. Since an InfoCube might have more that one InfoSource, the length of each may be an indicator of the InfoCube growth size as the company rolls out BW to other divisions. You should review of the design of InfoSources with large record lengths to determine the true need of including all the fields in the InfoCube vs. using alternate fields i.e. short text or codes, or removing them from the system..
Lessons Learned: Dont throw in the kitchen sink because it might come in handy one day..
12
Data Loads
BW Sources to InfoCubes/ODS and MultiCubes Sources
Infocubes Available options Jobcost details multicube* Jobcost history cube Options sold Pending close multicube (new)* MH AP line item cube MH AR line item cube MH general ledger cube General ledger line item ODS Cost cube MH property master (LOT) cube Purchasing item data Inventory cube Inventory multicube* PS controlling MH PS dates MH PS controlling and dates cube Earnest money estimation cube MHSD overview SD commissions cube Number 1 2 1 1 2 N/A 1 1 2 1 1 1 2 2 5 1 4 1 2 1 Complexity Low Low High Moderate Low High Moderate Low High Low Low Low Moderate Low High Moderate High Moderate High Moderate
When fixing data load problems, narrow the problem down quickly and focus on these areas. Most data loads can be de-coupled from each other in the process chains. This may reduce the time needed for activation
Lessons Learned: Spend your time and effort in a focused manner!!
13
Database statistics are used by the database optimizer to route queries. Outdated statistics leads to performance degradation.
Ledger BW index diagnostic BW diagnostic of statistics that is recommended to be updated User designed aggregates (performance & existence)
Outdated indexes can lead to very poor search performance in all queries where conditioning is used (i.e. mandatory prompts).
14
Programs that can help you monitor the system design: 1.SAP_ANALYZE_ALL_INFOCUBES 2.ANALYZE_RSZ_TABLES 3.SAP_INFOCUBE_DESIGNS
Explore the use line item dimensions for fields that are frequently conditioned in queries. This model change can yield faster queries
15
Validate the high-cardinality of the data and reset the flag if needed this will give a better index type and performance
16
A query now have to search in all InfoProviders to find the data This is very slow.
Solution: We can add hints to guide the query execution. In the RRKMULTIPROVHINT table, you can specify one or several characteristics for each MultiProvider which are then used to partition the MultiProvider into BasicCubes. If a query has restrictions on this characteristic, the OLAP processor is already checked to see which part cubes can return data for the query. The data manager can then completely ignore the remaining cubes.
An entry in RRKMULTIPROVHINT only makes sense if a few attributes of this characteristic (that is, only a few data slices) are affected in the majority of, or the most important, queries (SAP Notes: 911939. See also: 954889 and 1156681).
17
Generally, its recommended that you keep the number of InfoProviders of a MultiProvider to no more than 10 However, even at 4-5 large InfoProviders you may experience performance degradation
18
Since SAP BW 3.0B SP14 , you can change the default value of 30,000 rows Refer to SAP Note 629541, SAP Note 622841, SAP Note 607164, and SAP Note 630500
A larger number of base InfoProviders is likely to result in a scenario where there are many more base InfoProviders than available dialog processes, which results in limited parallel processing and many pipelined sub-queries
You can also change the number of dialogs (increase the use of parallel processing) in RSADMIN by changing the settings for QUERY_MAX_WP_DIAG.
19
20
BW 7.3 provides wizards to help you partition objects by year, business units or products.
Source: SAP AG, 2010
BW also generate automatically all needed DTP such as transformation rules and filters to load the correct infoProvider.
SAP suggests that this will make the maintenance is easier since any remodeling only need to change the reference structure.
SPOs can be added to MultiProviders for simpler query administration and to mask complexity
21
22
3. Read data during navigation and when expanding the hierarchy Data is read when requested by users in navigation
Key Feature: Reading data during navigation minimizes the impact on the application server resources because only data that the user requires will be retrieved
23
This places heavy demand on database and memory resources and may impact other BW processes A query read mode can be defined on an individual query or as a default for new queries (transaction RSRT)
SAP's recommendations for OLAP Universes & Ad-Hoc analysis (formerly: 'Webi'): 1. Use of hierarchy variable is recommended 2. Hierarchy support in SAP Web Intelligence for SAP BW is limited 3. The Use Query Drill option significantly improves drilldown performance 4. Look at the 'Query Stripping' option for power users. 24
If conditions and exceptions have to be used, the amount of data to be processed should be minimized with filters
When multiple drilldowns are required, separate the drilldown steps by using free characteristics rather than rows and columns
BENEFIT: This results in a smaller initial result set, and therefore faster query processing and data transport as compared to a query where all characteristics are in rows
This approach separates the drill-down steps. In addition to accelerating query processing, it provides the user more manageable portions of data.
25
Filters in Queries
Using filters contributes to reducing the number of database reads and the size of the result set, thereby significantly improving query runtimes.
Filters are especially valuable when associated with large dimensions, where there is a large number of characteristics such as customers and document numbers.
If large reports have to be produced, leverage the BEx Broadcaster to generate batch reports and pre-deliver them each morning to their email, PDF or printer.
27
The RSRT transaction is one of the most beneficial transaction to examine the query performance and to conduct 'diagnostic' on slow queries.
28
29
In this example, the basis team should be involved to research why the Oracle settings are not per SAP's recommendation
The RSRT and RSRV codes are key for debugging and analyzing slow queries.
30
We can see that the system creates a yellow flag for the 6 base cubes in the MultiProvider and the yellow flag for the 14 free chars.
HINT: Track front-end data transfers & OLAP performance by using RSTT in SAP 7.0 BI (RSRTRACE in BW 3.5)
31
Using RSRT you can execute the query and see each breakpoint, thereby debugging the query and see where the execution is slow.
Try running slow queries in debug mode with parallel processing deactivated to see if they run faster.
32
My Recommendation: Reduce RKFs in the query to as few as possible. Also, define calculated & RKFs on the Infoprovider level instead of locally within the query. Why?: Benefit: Formulas within an Infoprovider are returned at runtime and held in cache.
Drawback: Local formulas and selections are calculated with each navigation step.
33
34
The BI Analytical Engine and Sorting Sorting is done by the BI Analytical Engine. Like all computer systems, sorting data in a reports with large result sets can be time consuming. Try reducing the number of sorts in the 'default view'. This may improve the report execution & provide the users with data faster. User can then choose to sort the data themselves.
Reducing the text in query will also speed up the processing some.
36
37
38
41
This means that the query result set that was accessed by one user at 8:00am may no longer be available inmemory when another user is accessing it at 1:00pm.
Therefore, queries may appear to run slower sometimes.
The MDX cache is used by MDX based interfaces, including the OLAP Universe.
42
Distribution Types
You can increase query speed by broadcasting the query result of commonly used queries to the cache. Users do not need to execute the query from the database. Instead the result is already in the system memory (much faster).
43
44
To monitor the usage of the cache on each of the application servers, use transaction code RSRCACHE and also periodically review the analysis of load distribution using ST03N Expert Mode
PS! The size of OLAP Cache is physically limited by the amount of memory set in system parameter rsdb/esm/buffersize_kb. The settings are available in RSPFPAR and RZ11.
46
Change the logical file BW_OLAP_CACHE when installing the system (not valid name)
FILE
No central cache directory or lock concept (enqueue). The Set mode is not available by RSR_CACHE_ACTIVATE_NEW default. RSADMIN VALUE=x
Source: SAP AG 2010.
47
Roll memory was never maxed out in the period Paging memory was never maxed out in the period
48
49
Architectural Drivers
1990 Disk-based data storage Simple consumption of apps (fat client UI, EDI) Generalpurpose, applicationagnostic database 2010 In-memory data stores Multi-channel UI, high event volume, cross industry value chains Applicationaware and intelligent data management
2010
Improvement
0.05
MIPS/$
253.31
MIPS/$
5066x
Memory
0.02
MB/$
50.15
MB/$
2502x
Addressable Memory
216
100
Mbps
264
100
Gbps
248x
1000 x
Network Speed
5
MBPS
600
MBPS
120x
Physical hard drive speeds only grew by 120 times 50 since 1990. All other hardware components grew faster.
SAP BW
BI Analytical Engine 2. Indexes copied in to RAM on blades
InfoCubes
1. Indexing and compression stored on a file system
DSOs
51
Query Cache
Query Cache
Aggregates
SAP BW Accelerator
InfoProvider
Aggregates can be replaced with SAP BW Accelerator, while the memory cache is still useful.
52
Number of Queries
Seconds
Number of Queries
The major improvement is to make query execution more predictable and overall faster
Seconds
Health checks for SAP BW Accelerator are available under the transaction code RSRV
Plan for 2-5 days of SAP BW Accelerator training. You need a maximum of 1-2 administrators (1 for backup)
54
55
56
57
58
59
60
System issues can be hard to pin-down without access to EarlyWatch reports. Monitoring reports allows you to tune the system before user complains
61
This customer needed to improve the hardware to get the query performance to an acceptable level
62
In this example, we see that the EarlyWatch report found many known issues at the Oracle level that should be implemented before the performance tuning effort started.
Before the patches were applied it took 24 to 26 minutes to execute some queries, after the fixes, the queries ran at less then two minutes.
63
More at:
Performance tuning presentations, tutorials & articles www.ComeritInc.Com
SAP SDN Community web page for Business Intelligence Performance Tuning https://www.sdn.sap.com/irj/sdn/bi-performance-tuning ASUG407 - SAP BW Query Performance Tuning with Aggregates by Ron Silberstein (requires SDN or Marketplace log-on). 54 min movie. https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/d9fd8 4ad-0701-0010-d9a5-ba726caa585d Large scale testing of SAP BI Accelerator on a NetWeaver Platform https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b00e 7bb5-3add-2a10-3890-e8582df5c70f
64