PL-300: how to assess Power BI report performance (Performance Analyzer)
I will teach how to use the Performance Analyzer feature in Power BI Desktop to measure and improve report performance. This skill is useful for the PL-300 exam because it demonstrates that you can diagnose report bottlenecks and, in practice, ensures fast experiences for end users.
What you need to know
Performance Analyzer is a built-in tool in Power BI Desktop that records how long each visual and component takes to render. It identifies three main phases per visual: DAX Query (time to execute the query against the model), Visual Display (time to draw the visual) and Other (time for rendering engine interactions, for example, script execution). With this data you can discover whether the issue lies in the DAX query, the visual type itself, or in report-side transformations.
Simple example: a report has a table with thousands of rows and several cross filters. Performance Analyzer shows that most of the time is spent in DAX Query — a sign that the model query is heavy. Alternatively, if the time is greater in Visual Display, the problem may be the visual type (for example, a poorly optimized custom visual) or the number of points to draw.
How it works in practice
Follow this step-by-step to use Performance Analyzer and act on the results:
Open Performance Analyzer: in Power BI Desktop, on the View tab, enable Performance Analyzer.
Start recording: in the Performance Analyzer pane click Start recording to begin collecting metrics.
Interact with the report: refresh the page (Refresh) or interact with filters/slicers that typically cause slowness.
Examine entries: each listed visual shows times for DAX Query, Visual Display and Other. Click an entry and choose Copy query to copy the DAX query or the generated query for external analysis.
Interpret results:
- High time in DAX Query: optimize the model (relationships, columns, measures), review complex measures, use aggregations, or create indexes (when applicable in DirectQuery).
- High time in Visual Display: reduce visuals, use sampling for very dense charts, avoid unreliable custom visuals.
- High time in Other: check report interactions, bookmarks or scripts that run on render.
Test changes: after optimizing, record another session and compare times — the tool allows saving and exporting results for comparison.
Exemplo prático:
1. Abre o relatório problemático.
2. Start recording → Refresh visuals.
3. Performance Analyzer indica: Tabela A — DAX Query 3200 ms, Visual Display 200 ms.
4. Ação: analisar a medida usada na Tabela A, simplificar expressão DAX, evitar cálculos por linha.
5. Repetir gravação e confirmar redução do tempo DAX Query para, por exemplo, 400 ms.
Common mistakes
- Assuming all problems are DAX: many slow reports result from poorly chosen visuals or too many points to draw.
- Not comparing before/after: you measured an adjustment but didn’t record previous times — then you don’t know if there was an improvement.
- Ignoring impact of filters and slicers: a page with many slicers that apply complex filters can trigger heavy queries; test with and without them.
How to practice
Practice with real reports or samples (for example, the Sales Sample dataset). Use Performance Analyzer to record sessions before and after optimizations. For exam preparation, consult the OFFICIAL and free Microsoft Practice Assessment and the official study guide (also free) — both help confirm that you master the areas measured by the PL-300. Do not use or rely on exam dumps; always use official resources and hands-on labs.
In summary
- Performance Analyzer measures DAX Query, Visual Display and Other per visual — interpret each component to diagnose bottlenecks.
- If most time is DAX Query, optimize the model and measures; if it is Visual Display, simplify the visual or reduce data density.
- Always record before/after to validate improvements and test with the real filters and interactions of the user.
- Use Microsoft’s official resources (Practice Assessment and study guide) to practice and consolidate this skill for the PL-300.