Paginated Reports: Execution Time vs Time to Execute

[tommy_g]

Is there a way to capture execution time for a Paginated Report, as it runs on the service?

We have a complex report, broken into multiple sub-reports.

I can run each independently and would like to capture execution time, as in the difference between running the report and the time rendering has completed. I know the "meta" answer right now, namely "too long". 

I know how to do this in an Event Driven report such as Access. I don't see any event driven behavior surfaced to the developer in Report Builder. 

[v-stephen-msft]

Hi @tommy_g ,

I found these similar posts which provide some methods, please kindly refer to:

PAGINATED REPORT EXECUTION TIME

Paginated reports date and time returns GMT timezone on PBI service

Execution Time Changes on PBI Service for Paginated report

Best Regards,

Stephen Tao

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[tommy_g · Accepted solution]

Helpful in that one of the links references the @Now function. Since the report has 6 subreports, I imagine there will be different values which can help approximate elapsed time. Of course I don't know what happens behind the scenes, there might be a lot of setup which elapses before the first @now function call happens. I know some (or all?) report writers use at least two passes, to calculate total page count and build a document map with page links. Sadly, no document map in PBI Paginated. Since bookmarks are not supported either, it may be the case that pages are rendered one at a time. That's what appears to happen when viewing in Page format on the server.