SAP BO web intelligence reports performance tunning guidelines

Below are performance tuning guidelines for webi report development.
These guidelines needs to be followed with Universe performance tuning guidelines
given separately on this blog to get good performance reports.

• Avoid using larger number of reports in same document

• 10 reports per document is a reasonable number
• Do not exceed 20 reports per document

• Don’t try to account for all scenarios in one document but rather focus on specific scenarios that add value to the consumer.

1. 50,000 rows per document is a reasonable number
2. Do not exceed 500,000 rows per document

• Limit the number of Data Providers used

• Best Practice from the field is to use no more than 15 Data Providers per document
• Data providers run serially so run times add up
• Refresh time and merging of dimensions can cause some big delays on the Processing Server side

• Create smaller, reusable documents
  By creating smaller, reusable documents you:

• Reduce the time it takes to load the document in the viewer
• Reduce the refresh time
• Reduce the system resources needed on both the client and server side
• Improve the performance

• Use Report Linking

• Instead of using HUGE documents, consider using smaller documents and linking them together!
• Link reports together using OpenDocument linking and a combination of Prompts and Filters.
• This removes performance hits for unnecessary parts of the report.

• Avoid Auto-Fit/ auto Width of fields wherever possible.

• Avoid Nested Sections

• Nested sections can contribute to performance degradation issues.

• Try to use Query Drill

• Reduces the amount of data stored locally for a drill session.

• Limit use of Scope of Analysis by removing not required objects from Scope of analysis.

• Limit the number of variables/formulas and try to push complex calculation or formulas to Universe or DB level.