Report Execution In Report Studio vs Cognos Connection

[CognosMyCognos]

When running a report that renders as a .pdf, it runs pretty quickly within RS but slows to a crawl when run via the portal. 

Is there any difference in the way reports are run when you run them from RS versus the portal?

thanks

[blom0344]

What happens with the main Cognos process on the server (BIBUSTKServerMain.exe) ? When the report is crawling, what happens with this proces. Do you have a means to monitor this?

[CognosMyCognos]

The BIBusTKServerMain.exe registers a quick blip of activity and then goes back to using 0 CPU.

After further investigation, I've determined that it really isn't an issue of run time in RS versus Cognos Connection.  The real issue here seems to be with the rendering of the report output.  When I run as HTML it comes back in a heartbeat but when I render as a .pdf it takes forever.

Through "run with options" I see that when I save the output both as HTML and .pdf the report takes about 5 minutes to return.  So the HTML coming back in a "heartbeat" is most likely because the entire report isn't being rendered.

But what I can't figure out is why this report take 5 minutes to run.  It's not insanely complex (9 non-prompt queries that all are joined within the report) and a previous version of this report (written against an old model) rendered the .pdf very quickly.  And it's not churning through a ton of rows to produce the 5 page output.

I'm guessing is might have something to do with the date processing I have to do but the old report did the same thing.

I know this question is hard to answer without knowing more about the report but are there any generic tips to get reports with multiple queries to run faster?