PL-300 · Question #371
You have a Microsoft Power BI report. The size of PBIX file is 550 MB. The report is accessed by using an App workspace in shared capacity of powerbi.com. The report uses an imported dataset that cont
The correct answer is D. Split the visuals onto multiple pages.. To improve Power BI report performance when a single page has too many visuals, distributing the visuals across multiple pages reduces the processing load per page view.
Question
You have a Microsoft Power BI report. The size of PBIX file is 550 MB. The report is accessed by using an App workspace in shared capacity of powerbi.com. The report uses an imported dataset that contains one fact table. The fact table contains 12 million rows. The dataset is scheduled to refresh twice a day at 08:00 and 17:00. The report is a single page that contains 15 AppSource visuals and 10 default visuals. Users say that the report is slow to load the visuals when they access and interact with the report. You need to recommend a solution to improve the performance of the report. What should you recommend?
Options
- AChange any DAX measures to use iterator functions.
- BImplement row-level security (RLS).
- CReplace the default visuals with AppSource visuals.
- DSplit the visuals onto multiple pages.
How the community answered
(30 responses)- A7% (2)
- B3% (1)
- C13% (4)
- D77% (23)
Why each option
To improve Power BI report performance when a single page has too many visuals, distributing the visuals across multiple pages reduces the processing load per page view.
Changing DAX measures to use iterator functions may optimize specific calculations but is not a primary solution for the overhead caused by an excessive number of visuals on a single page.
Implementing row-level security (RLS) adds filtering overhead and does not directly address performance issues stemming from too many visuals.
Replacing default visuals with AppSource visuals is likely to worsen performance, as AppSource visuals can sometimes be less optimized or heavier than built-in visuals.
A single page with 25 visuals (15 AppSource + 10 default) significantly increases the number of queries and rendering tasks required when the page loads or interacts, leading to slow performance. Splitting these visuals onto multiple pages reduces the computational burden per page, improving loading times and responsiveness.
Concept tested: Power BI report performance optimization
Source: https://learn.microsoft.com/en-us/power-bi/guidance/power-bi-optimization#general-performance-tips
Community Discussion
No community discussion yet for this question.