cancel
Showing results for 
Search instead for 
Did you mean: 

WEBi BW BICS 4.0 Slow Issues

Former Member
0 Kudos

Experts -

We are using BICS to get data from BW into Webi Reports.

System Details:

BOBJ 4.0 Patch 14

BW 7.0 EHP5

We are facing extremely slow performance when running the Webi reports from launch pad.

  1. Opening the Webi Report: The time it takes to open the prompt screen is around 30secs for small reports. Its more than 1 minute for large reports. In BW, the time it takes to open the prompt screen is 2-3s independent of size of the report.
  2. List Of Values Refresh - LOV refresh is pretty quick (3-4 secs) for info objects with less list of values like country. But its more than 2 minutes for info objects like Employee or Position where list of values is 100K plus. It gives partial results after 2 minutes. Again on BW side, it takes 4-5 secs to open list of values for Employee or Position.
  3. List of Values Search - Same behaviour as above. Search is very slow for Employee or Position. More than 2 minutes.
  4. Report Run time - And lastly report runtime in also very slow. The report that takes 5-10 secs in BW takes more than 1 minute in Webi.

I have shown comparison with BW because we are trying to move the users from BW to BOBJ. I understand that the performance in Webi can never be same as BW but its very slow compared to BW. I will be very happy if Webi is half as fast as BW.

Please suggest what can be done to improve the performance in the 4 areas I explained above. Appreciate your help.

Thanks,

Tarun

Accepted Solutions (1)

Accepted Solutions (1)

Henry_Banks
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

in the current product, the larger your Bex query, the longer the initialization time.

here are some suggestions off the top of my head:

1. make your bex query as 'lean' as possible . i.e. not 1-size fits all

2. add default values to your bex query variables

3. avoid use of refresh on open in webi

4. use the (dhtml) web view preference, rather than java

5. exclude unassigned nodes for hierarchies in RSH1

6. avoid use of Structures in bex query

7. tick 'use of structure elements' in RSRT

8. increase the Tomcat configuration – increase memory pool

9. increase the Java 32 client runtime parameters

10. enable query stripping in webi query panel and document properties

11. Implement the best-practice from this note :  1694041 - BI 4.0 Consulting:- How to size the Adaptive Processing Server 

12. take a look at this webi design document especially the section 'refactoring queries'  https://service.sap.com/~sapidb/011000358700000750762010E

Regards,
H

Former Member
0 Kudos

Hi Henry, can anyone share your experience on the steps that you did for performance improvement when webi documents are opening on the CRM portal. we are trying to display the data for customer and we have integrated 3 webis on the CRM portal. The back end is HANA. For few big customers it takes a lot of time and there is a timeout in the portal. Can any steps be taken from the webi end to improve the performance?

Answers (0)