We are working in BO 3.1 with SAP Integration in place.
In one of our Xcelsius dashboards we have 4 crystal reports and a webi report. The data in the report is coming from SAP BW ,so to avail data level security we have checked the option ‘Refresh on Load’ for the dashboard.
As some the base reports for dashboards are bulky and take time to refresh, it is causing a remarkable delay to load dashboards for end users.
Is there a way we can improve the dashboard load performance without losing our grip on BW security. I think scheduling will not solve our purpose as it will again bypass the BW security.
well…your dashboard can’t refresh any quicker than it takes for the reports to refresh, so your only option will be to improve the reports to run quicker.
The problem here is that individual reports are not taking that much time.
There is only one report that shows inconsistent behavior while refreshing. Sometime it comes up very quickly and at times it gets hanged. That reports is based on BEX query and running very fast in BEX environment.
Is there a way I can dig to the root cause of the problem.
It is difficult to make users understand about it as they are saying everything is so fast at BEX level.
Will really appreciate if anyone can share his thoughts on that.
Hey Chandra: Currently, I am floating in the same boat as you are.
My tests using QaaWS had come with resultrs nothing fast. Each QaaWs used within the Dashboards takes up to 10 second to refresh and havind aroung five QaaWS in a single Dashboard it takes an eternity for the users to wait for the results (initial load).
I am using MS-SQL 2005 SP3 as a CMS repository and business Databas in a box and BO Xi 3.1 over Tomcat in another machine.
Tha fact that sometimes seems to render faster than others, may obey to the use of cache that (by default) is set to 120 seconds. If the dashboard will render faster is load inmediattely (within the 120 seconds) after the first time it was load.
If you find a solution, let me know…Currently I am not seing one, rather than use pre-query results from a pre-fetched report.
There are a number of suggestions that we got from BO experts.
One of which says that the long initialization time could be due to the presence of corrupted objects (or components). This may happen during the course of development time when you add the components to your dashboard.
We started with the older version of dashboard that having fewer objects and added required objects again.
Now , the new dashboard that we build in this manner is showing a lot of performance improvement though it is exactly same as of the one which was taking time to load.
To discard complex query is taking the big tool on this Dashboard where three bog complex query takes 10 second each to refresh, we decided to create a display of three easy queries, simply pulling information of a single table with few filters on it. In that specific case, the dashboard also took 10 second per query to refresh.
The test was performed against the same database in MS-SQL 2005 and the same universe.
Followed, I conducted another experiment where the data was on a CSV file in the web/app server and I built a universe pointing to this CSV file. Created a QaaWS to pull data from that CSv file and called it from the Dashboard. I was surprise to see the Dashboard refresh in less than a second…Three queries like that refresh in a two seconds…But I cannot find where the delay accessing the MS-SQL server is.
(BOB member since 2006-10-09)
(BOB member since 2004-10-01)