If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Speed up huge active report?

Started by charlie, 17 Dec 2018 08:30:13 AM

Previous topic - Next topic

charlie

Hi Gurus,

I was wondering if there is anything that I can tinker with to speed up the performance of one of my huge active reports. The report output size is around 90 MB (I know it's way too much but cant help it). All my queries (50 of them) run real quick (15-20 secs each) but the report still takes about an hour and a half to generate. So i suspect the bottleneck is when Cognos is writing to the report output. Are there any settings that I can play around with to speed things up?

I've attached the Info properties for my report. Any ideas?

Thanks in advance!

Best,
Charlie

SGD

Quote from: charlie on 17 Dec 2018 08:30:13 AM

I was wondering if there is anything that I can tinker with to speed up the performance of one of my huge active reports. The report output size is around 90 MB (I know it's way too much but cant help it). All my queries (50 of them) run real quick (15-20 secs each) but the report still takes about an hour and a half to generate. So i suspect the bottleneck is when Cognos is writing to the report output. Are there any settings that I can play around with to speed things up?

I've attached the Info properties for my report. Any ideas?


Ideally, Cognos Active Report .MHT file size shouldn't be more than 10MB. It is bound to take hell lo of time to generate the output if size is around 90MB.

Active Reports renders the data at runtime, encapsulates them into an .MHT file, and then sends that file out.

I have encountered this issue before and only solution I did to split the report functionalities in separate Active reports to make each one lightweight i.e <= 10MB.

Regards,
S.G.D.
Regards,
S.G.D.

charlie

#2
Thanks for your response SGD! I know this is way beyond what the ideal size should be :( And that's why I am looking for any hack that can help speed up the report generation.

I am thinking on the lines of some configuration setting at environment level that can provide more resources to the active report generation process. Would anyone know the inner workings of the process that is followed (services used, high/low affinity connections, memory used, etc, etc.) when an active report is run. I know that it relies on the batchReportService same as any other scheduled report, but anything else?

Thanks again!