COGNOiSe.com - The IBM Cognos Community

IBM Cognos 8 Platform => COGNOS 8 => Report Studio => Topic started by: Prakash Bhai on 25 Jan 2012 12:37:10 AM

Title: how to improve performance of the report without disturbing existing query
Post by: Prakash Bhai on 25 Jan 2012 12:37:10 AM
Hi All,

Currently, the report takes more than 50s to show results, our target is within 45 seconds. need to improve this without disturbing existing query'


Regards

Ram
Title: Re: how to improve performance of the report without disturbing existing query
Post by: charon on 25 Jan 2012 02:51:59 AM
hi,

considering the amount of information (what kind of report, drills, rel or dim/drm, prompts and so on) you deliver theres not a lot i can tell you.
Performance issues are often handled on the etl level, but if you want to increase performance of the report...check the proven practises of ibm out
http://www.ibm.com/developerworks/data/library/cognos/cognosprovenpractices.html
there are a lot of performance articles as well.
E.g., if you use Master-detail-rel this might help
http://www.ibm.com/developerworks/data/library/cognos/reporting/performance_and_tuning/page582.html
hope you will find what you need :)
cheerz :P
Title: Re: how to improve performance of the report without disturbing existing query
Post by: charon on 25 Jan 2012 02:52:53 AM
btw, 50 sec is not THAT much ;)
Title: Re: how to improve performance of the report without disturbing existing query
Post by: blom0344 on 25 Jan 2012 09:15:54 AM
50s vs 45 seconds is really a questionable requirement. There are a lot of variables to be considered (available memory/ uptime server/ number of connections / concurrent requests) so there is a natural variance that may result in 5-30 % difference with the same report and dataset. Not to mention caching effects when exactly the same results are requested.
And indeed 50sec ?  Ain't bad for a real report
Title: Re: how to improve performance of the report without disturbing existing query
Post by: mmcalli on 03 Feb 2012 10:22:57 AM
If the report is not prompted, then schedule the report to run on a regular schedule and save the results, and make the default way of opening the report to be to display the last saved report.

Alternatively, if your report is prompted, and it's running against a database, work with your DBA to either add indexes, save a better execution plan for the query, or maybe even come up with a materialized view with query rewrite enabled.

Mike