Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
So i recently moved my power bi assets from Power BI service to my self hosted report server. I noticed it seems loading a report loads slowly when compared to power bi service. I am using a good remote server that has some capacities. I have done the best practices like reducing the joins in the report, cut schedule refresh, and optimizing queries, using the performance analyzer on desktop shows positive result too. Stakeholders get pissed off when it takes forever to see anything on their screen. Can anything be done to mitigate this?
It run faster in our local server than in the closest datacentre in our tests.
I used a very simple report for testing, which can be opened in the cloud in about 3 seconds, but it takes 5 seconds locally
First, analyse ExecutionLog3 to check what is slow, if model processing, open report definion, model loading to memory, or dax queries. Second, check you server resources, especially memory a CPU utilisation. Also check how often are report wipe-out from memory.
For comparsion, in my enviroment, I must install second PBIRS server in scale-out mode, and dedicate background model processing to second server (and first server only as PBIRS front-end). My experience, model processing, and also dax query performance is fully comparable to cloud Power BI Service. But report open (authentificate and definition load) and load model into memory (if not already loaded), is little slow (but not big difference}
On Front end servers, find rsreportserver.config file in your instalation folder. And set <IsDataModelRefreshService> to false.
thank you
First, analyse ExecutionLog3 to check what is slow, if model processing, open report definion, model loading to memory, or dax queries. Second, check you server resources, especially memory a CPU utilisation. Also check how often are report wipe-out from memory.
For comparsion, in my enviroment, I must install second PBIRS server in scale-out mode, and dedicate background model processing to second server (and first server only as PBIRS front-end). My experience, model processing, and also dax query performance is fully comparable to cloud Power BI Service. But report open (authentificate and definition load) and load model into memory (if not already loaded), is little slow (but not big difference}
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |