Breaking down report execution times?

[DFWCognosGuy]

First, let me say that I searched the forums and I didn't find this particular question, so if it has been asked and answered before, please forgive me!

Okay, is there a way to break down the execution time of a report to know how long it took Cognos to retrieve the data and how long it took Cognos to process the data?  Just looking at the audit database, I see no table/columns that would give this.  A Cognos solutions guy said that it was possible but you had to drop some XML file (or something) on the server to get that kind of information.  Has anyone had any success in doing something like this?  I am trying to identify reports that run a long time because it is pulling back a ton of records (and Cognos of course is having to process those records.)

Any help or insight would be appreciated.  Thanks!!!   ;D

[o-time]

I'm not 100% sure but I believe you can view that by increasing the logging levels on the report service .  There is a program in the Cognos bin folder called logconsole which will organize and breakdown the log files so you can query them easier. It might be helpful once you have a higher logging level configured.

[Suraj]

There was a technique that involved adding a javascript file in <install_location>/webcontent/samples/ folder.
Here is a portion of the article:
When reports are being developed, it is often useful to have an idea on amount of time it takes
for a report to run. Knowing how long it takes to run a report can lead to more efficient report
design and can be used to help set the expectations of the report consumers.
The approach described here is completely self-contained on client side. This means that a report author can obtain the times without the need to view or access to various log files.
This approach requires the use of a control page that will set the starting time. In this example a prompt page will be used as the control page. If there are multiple prompt pages to the report, the last prompt page should be used as the control page.
When the Finish button is clicked from the prompt page, the start time will be taken and stored in a cookie. The end time will be taken when the browser begins to render the report output. The elapsed time is calculated by subtracting the start time that was stored in a cookie with the end time. Note that this approach only applies to HTML output.
This technique was tested against Cognos ReportNet 1.1 MR2 and MR3 as well as Cognos 8 MR2.

[swordfish]

I'm not 100% sure but I believe you can view that by increasing the logging levels on the report service .  There is a program in the Cognos bin folder called logconsole which will organize and breakdown the log files so you can query them easier. It might be helpful once you have a higher logging level configured.

Increasing the logging level also complicates things. The log also captures the processing time for every query in the report and that includes the time taken to process the prompts (also queries). To add to this, if we do load testing on 10 reports with 10 prompts each, you can imagine how many queries get logged in the log file with no particular order.