The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Hi,
I'm publishing my power bi reports (which is live connecting to SSAS) to PBIRS.
For the first time load the report in PBIRS portal, it takes 3-4 minutes which is very slow even when the amount of data in SSAS is not big.
Once reports are loaded, it appears quickly when I hit refresh.
Has anyone overcomes this issue before? Please help.
Thank you.
@npvinhloc Well, could be one of two issues. One, PBIRS is not warmed up or if not that then the first time you are hitting the live connection it is pulling from the source whereas after that perhaps it is hitting cache.
Warming up SSRS? – SQLServerCentral Forums
I'm using SSAS + Power BI live connection, so it's might not be the cache. As once the visuals are loaded I can interact with them and performance for re-rendering those visuals is good.
So it could be the server is not warmed up. But when I tried with incognito browser to access the same report, it still take very long.
I performed steps below:
@npvinhloc Here are some possible solutions:
Troubleshooting - Solved: Slow On-Premise Report Server Performance /powerbi... - Microsoft Fabric Community
Custom visuals - Slow Custom Visuals In Power BI Report Server | Power BI (devoworx.net)
The thing is, no report is opened at that time, I just go to <host>/reports; this should be the home page with list of reports and folders only.
Then I did a check by hitting F12 and found that it took more than 2 minutes (over 3 minutes in total) to load 2 js files for the first load.
I'm not sure those js files are statics and could be cached or it's something else from PBIRS.
(I'm not having good knowledges about web stuff)
Hi, @npvinhloc
Large JavaScript (JS) files or other non-cached resources may cause slow initial load times.
Solution:
Ensure that static resources such as JS files have appropriate cache headers. Use a Content Delivery Network (CDN) or optimize network paths if PBIRS is hosted remotely.
If the service account used by PBIRS does not have the appropriate permissions or is configured incorrectly, it can cause delays.
Solution:
Ensure that the service account has the necessary permissions on both the PBIRS and SSAS servers. Verify the impersonation mode in SSAS, as incorrect settings can cause performance issues.
Start SQL Server Profiler and connect to your SSAS instance.
Start a new trace, load a report, and see which queries are running and how long they take.
Use Task Manager or Performance Monitor on the PBIRS and SSAS servers to monitor CPU, memory, and disk I/O.
Check for high usage spikes during the initial report load.
Review the PBIRS log: The PBIRS log can typically be found at C:\Program Files\Microsoft Power BI Report Server\PBIRS\LogFiles. Check the log for any performance-related errors or warnings.
Create a simplified version of the report with fewer visuals to see if it loads faster.
Identify complex visuals: Gradually add visuals to determine if a specific visual is causing the delay.
hackcrr
If I have answered your question, please mark my reply as solution and kudos to this post, thank you!
@npvinhloc Hmm. Good test. I would say that rules out PBIRS warm-up. Let me do some digging and see what I can find.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.