topic Re: Paginated Report slow first time it is run (Power BI Report Server -on prem) in Report Server

Paginated Report slow first time it is run (Power BI Report Server -on prem)

gwhiteman — Thu, 17 Feb 2022 21:04:49 GMT

I have several paginated reports that are very small and quick to run.
I have loaded them onto our Power BI Report Server (on prem) and noticed that first time take >30 seconds to run.
After that first run, they run return almost immediately.

These are the only two paginated reports and they are NOT in high use. I am assuming the service is starting up for during the first 30 seconds. Is there a way I can 'warm up' the service?

Re: Paginated Report slow first time it is run (Power BI Report Server -on prem)

d_gosbell — Fri, 18 Feb 2022 06:19:16 GMT

gwhiteman wrote:

I am assuming the service is starting up for during the first 30 seconds. Is there a way I can 'warm up' the service?

I do not believe this is the source of your issue. I've never witnessed this sort of issue on any of our Report Server environments.

I would suggest checking the ExecutionLog3 view in the ReportServer database for these reports. This should give you a breakdown of the query time and the rendering time for each report run. One other possibility is that this could be caused by a delay in authenticating to the source database.

But if you don't see any difference in the ExecutionLog3 view then I would suggest checking the Report Server log files as there may be some messages in there that will give you a hint as to what is causing this delay.

Re: Paginated Report slow first time it is run (Power BI Report Server -on prem)

Anonymous — Mon, 12 Jun 2023 16:04:10 GMT

Hi gwhiteman ,

could you please let me know how you resolved this issue, i am also facing this issue. Initially it take around 45 - 50 secs in later runs its coming under 25 secs.

Re: Paginated Report slow first time it is run (Power BI Report Server -on prem)

DavidSie — Mon, 26 Jun 2023 11:55:15 GMT

PowerBI Report Server and SSRS are trying to reach out for some MS metric servers on first report execution. You can monitor this in your browser and disable it by configuration or regedit. In my case this was the cause for slow initial report loading while the firewall didnt allow it and the requests timed out.

Re: Paginated Report slow first time it is run (Power BI Report Server -on prem)

gwhiteman — Mon, 26 Jun 2023 12:25:34 GMT

Hi Anonymous,
I don't recall what was done to resolve this problem as I did not install/maintain the servers. I vaguely remember we changed some HA settings and update our Oracle drivers. Sorry I can't be of more help. \]

Re: Paginated Report slow first time it is run (Power BI Report Server -on prem)

MarkPalmberg — Sun, 22 Dec 2024 17:07:51 GMT

Do you recall exactly which configuration setting this was? I have a paginated report that takes a number of seconds to load initially, and I'm trying to resolve that. Is it related to this?

Re: Paginated Report slow first time it is run (Power BI Report Server -on prem)

gwhiteman — Wed, 12 Feb 2025 07:12:21 GMT

Sorry that was a long time ago, I don't recall what the changed was.

Re: Paginated Report slow first time it is run (Power BI Report Server -on prem)

gwhiteman — Wed, 12 Feb 2025 07:13:50 GMT

We also moved from Report Server to Power BI Service.

Re: Paginated Report slow first time it is run (Power BI Report Server -on prem)

MarkPalmberg — Wed, 12 Feb 2025 14:33:57 GMT

How are you finding your RDL performance in the service? That's where our issues are, and they seem to do with loading parameters on the initial load of the report.

Re: Paginated Report slow first time it is run (Power BI Report Server -on prem)

gwhiteman — Wed, 12 Feb 2025 18:47:20 GMT

We find hte performance in the service was great. It was only when running Power BI Report Server on prem we experienced it.

Re: Paginated Report slow first time it is run (Power BI Report Server -on prem)

MarkPalmberg — Wed, 12 Feb 2025 19:09:29 GMT

Are you using a gateway to connect to your SQL server? Or are you connecting directly to Azure SQL server instances?