Power BI Report Server Extremely Slow

[Anonymous]

Hi.  Would someone be able to direct me to a person or persons who can look into the ridiculous slowness with the Power BI Report Server of late?  It is taking forever to load dashboards, to the point where I'm being contact by analysts who think the dashboards are broken.  It's always been slow, but it's gotten much worse lately. 

Thank you.

[stretcharm]

Do they load slowly in the Desktop?

Check this out @cwebb on how to use daxstudio and sql profile to see your m query performance.

https://blog.crossjoin.co.uk/2019/02/09/power-query-execution-times-using-sql-server-profiler/

I've also got a powerbi to help you read them

https://github.com/stretcharm/PowerBITraceFiles

You can also trace sql if that is your source to see how long the queries are taking

Usually when I have issues Its my db that is the bottleneck.

Also be aware that if you have queries that reference to other queries may end up running in parallel and resulting in the same query being requested multiple times.

[Anonymous]

Hi.  Thank you for your response, and apologies for the delayed response.  The site is experiencing slowness with all pre-existing dashboards, not just the one I'm working on, and it's been a sporadic issue over the past year.  Still, I'll check out your suggestions.

-E

[Anonymous]

We recently found our server slowing down considerably.  Once the PBI reports were up they seemed to be pretty fine. We eventually tracked it down to the AntiVirus running on the Server. This was causing a lot of latency in spinning up the captive SSAS instance and data sets in the background as reports were running. We excluded the PBI Report Server install directory from the AV active scanning. It certainly helped though the network scanning stuff still seems to be giving us some delays/issues.

[ITGeek555]

I would also look into the resourcing on the server hosting PBIRS.  Noting that the reports are 'rehydrated' from the database into local SSAS instances on the server, if there is insufficient RAM to hold all active reports and spare RAM to support refreshes to import mode models then PBIRS will have to prune out the least recently used report.  It may be that there is a lot of report churn occurring due to increased usage of the service.  You can review the PBIRS capacity planning white paper to see if your server provides the required resources.