Hi,
I’m working on Dashboards 4. My dashboard has connection to webi via web services. Under the Web service ABC, I have total of 13 Blocks, so there are 13 QAAWS set up.
I have put in Input Values, for ‘Refresh’, value of 1 in each of them…
This will refresh Data as things change every month. However it takes too long.
My swf file is 1.31MB
what can I do to make the performance improve?
As a note, that is refreshing the report 13 times. I know that is counter-intuitive, but that’s how it works. Thus, it takes a while. Also, it can cause issues, as having one user refresh the same report 13 times simultaneously can cause the WebI Processing Server to lost track of what it is doing.
Best practice from SAP is that each web service should point to a separate report. We have found that it is best to have each point to separate document. We just had to go back and redesign all of our dashboards, because we had gotten complacent about that and every dashboard started throwing errors.
Have you tried redesigning it a bit to use the latest instance, instead of refreshing the report? That makes an enormous difference in speed. And if you are pointing to some kind of EDW that only refreshes once a day anyway, the currency of the data is irrelevant.
The poor performance may not only be about the BIWS retrieval time. What are you doing with the data once it’s been returned from the BIWS? Lots of nested calculations, using chart components with a large series ranges, daisy chaining formulae etc, can all hinder the overall performance of the dashboard.
AmericanMC, Good points from Cdavies. Additional to it, the number of rows you are bringing back to the excel model within the Dashboard also make it slow. The bigger the number of rows, then slower the model is.
In the past, I used more than 13 QaaWs from a Dashboard to pull information from a single Webi report that refresh once a week which have 6 different TABS. Some of those QaaWs refresh upon changing the data in the Dashboard, but most of those refresh upon the xcelsius is loading.
NOTE: Bringing the data into the Dashboard doesn’t mean the report need to refresh. The QaaWs is refreshing to bring the data (whatever it is in the report at that moment). Of course the Webi can be set to refresh upon action in the dashboard, but unless it is a real-time report/Dashboard I would stay-away from this practice.
If you want t troubleshoot performance and see which QaaWs is in fault (using IE) you could go to F10> Tools Menu> Developer Tools(F12)> to track and see the HTTP request.
Each QaaWs will be exposed while tracking/running the dashboard and you’ll find out the QaaWs block you need to improve.