COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Report Studio => Topic started by: tarunkrdas2013 on 14 Sep 2015 05:33:17 PM

Title: RePORT Performance down after Rows per page set as 100000
Post by: tarunkrdas2013 on 14 Sep 2015 05:33:17 PM
Hi ,mine is crosstab tab report nested under list report (its a requirement as we are changing from cube to DMR).Output is Weekly sales shown per Fiscal week and there is a section at Fiscal week ,hence i want all week lke fiscal week 1 fiscal week 2,fiscal week 3, fiscal week 4 data in one page ,current report with cube package has "Rows per page " property set as 100000 but when i put the same setting with DMR package i.e. i put "Rows per page " property set as 100000 ..performance of report goes slow like fiscal week 1 fiscal week 2,fiscal week 3, fiscal week 4 data comes at 1minute 30 seconds .

When i remove the setting "Rows per page " to 0 ,i see good perfromace i.e. output comes at 14 seconds,can anyone suggest what can i do achieve good performance
Title: Re: RePORT Performance down after Rows per page set as 100000
Post by: Francis aka khayman on 15 Sep 2015 03:42:17 AM
when you set rows per page to 100000, all rows get retrieved which i will guest take significant amount of time before your output is displayed.

when you remove rows per page value, the report retrieves the minimum number of rows and display your output. the rest of the rows get retrieved when you click "Next page" Or something like that, hence you get the impression that the performance is "better".
Title: Re: RePORT Performance down after Rows per page set as 100000
Post by: MFGF on 15 Sep 2015 04:37:07 AM
Quote from: khayman on 15 Sep 2015 03:42:17 AM
when you set rows per page to 100000, all rows get retrieved which i will guest take significant amount of time before your output is displayed.

when you remove rows per page value, the report retrieves the minimum number of rows and display your output. the rest of the rows get retrieved when you click "Next page" Or something like that, hence you get the impression that the performance is "better".

Nobody seems to be mentioning the elephant in the corner? We can all see it's there, though. Ok - I'm going to. :)

What possible business use would a person gain from a 100,000 line report? Seriously? That's not a report, it's a data dump. Who is ever going to read it? It's longer than a novel, and not remotely as interesting. Why wouldn't you focus on what's important rather than just spewing out all the data on the page?

Ok - now we can all relax - the elephant has been identified :)

MF.
Title: Re: RePORT Performance down after Rows per page set as 100000
Post by: Francis aka khayman on 15 Sep 2015 04:54:22 AM
after years of evaluating user requirements and user requests for Cognos reports, seeing an elephant in the corner would be the least weird thing
Title: Re: RePORT Performance down after Rows per page set as 100000
Post by: Lynn on 15 Sep 2015 07:11:47 AM
Quote from: khayman on 15 Sep 2015 04:54:22 AM
after years of evaluating user requirements and user requests for Cognos reports, seeing an elephant in the corner would be the least weird thing

That is so true and very funny. I did an Applaud since there isn't a Like feature on the forum

;D
Title: Re: RePORT Performance down after Rows per page set as 100000
Post by: tarunkrdas2013 on 15 Sep 2015 11:28:08 AM
I thank everybody for your to the point analysis ,i will try to give explanation to  business users to have a Fiscal week 1 on page and Fiscal week 2 on next page so as to have better analysis and not big data dump