Performance Analyzer

Power BI · Advanced Features

Theory

Performance Analyzer in Power BI Desktop records how long each visual takes when a page is rendered or a user interacts. You open the pane, click Start recording, then refresh visuals or click slicers. For each visual it lists the total duration broken into parts: DAX query (time for the engine to return the data), Visual display (time to draw the visual) and Other (time waiting, for example behind other visuals or for background work).

The pattern of numbers tells you where to look. A long DAX query points to an expensive measure or model design, such as a FILTER over a whole fact table or many-to-many relationships. A long Visual display points to too many data points or a heavy custom visual. A long Other often means too many visuals on the page. You can copy the query of any visual and run it in DAX query view or an external tool such as DAX Studio to test improvements.

Why we use it

Slow reports frustrate users and get abandoned. Performance Analyzer replaces guesswork with measured timings, so you fix the actual bottleneck.

When to use it

Use it before publishing any important report and whenever users complain about speed. Test with a cold start using Refresh visuals, and compare before and after each change. For refresh (not rendering) slowness, look at Power Query and source performance instead.

How it works

  1. Report page feels slow
  2. Start recording and refresh visuals
  3. Find the visual with the longest duration
  4. Is the DAX query the largest part? Yes: Optimise the measure or model. No: Reduce visuals or data points.
  5. Record again and compare
  6. Page renders faster

Syntax

Desktop: Optimize ribbon → Performance analyzer (older versions: View → Performance analyzer)
Start recording → Refresh visuals / interact → Stop
Per visual: DAX query | Visual display | Other → Copy query / Run in DAX query view

Example

1. Open the Sales Overview page → Performance analyzer → Start recording → Refresh visuals.
2. The bar chart's DAX query time is much longer than the other visuals.
3. Copy query: the measure uses CALCULATE([Total Sales], FILTER(Sales, Sales[Region] = "North")).
4. Rewrite it as CALCULATE([Total Sales], Sales[Region] = "North") (column filter, not a table scan).
5. Record again and compare the DAX query time.

Key points

Power BI topics

Power BI Introduction

Getting Data

Power Query (Data Transformation)

Data Modeling

DAX (Data Analysis Expressions)

Data Visualization

Dashboards & Reports

Power BI Service

Advanced Features

Projects & Case Studies

Interview & Certification

Advanced DAX & Time Intelligence

T
Tech Town
Log InSign Up Free
Home SQL Python DSA Power BI Snowflake Databricks Spark Gen AI Practice Problems Contest Blog

Power BI Dashboards & DAX

Learn data visualization and interactive dashboards step-by-step. Click any topic in the sidebar to open it right here.

{{ sectionCount }}
Sections
{{ topicCount }}
Topics
Free
Forever
Hands-on practice Practice DAX Online 250 business scenarios on a star schema — write a measure and compare your visual with the expected one. Start practising →
Section {{ sec.num }}

{{ sec.label }}

Power BI  /  {{ current.sectionLabel }}  /  {{ current.name }}

{{ current.name }}

Theory

{{ current.def }}

Why we use it

{{ rich.why }}

When to use it

{{ rich.when }}

Diagram

{{ rich.dg.caption }}

{{ tb.title }}
{{ c.v }}
{{ rich.dg.op }}
➜
{{ rich.dg.output.title }}
{{ c.v }}
{{ nd.label }}
{{ nd.sub }}
{{ nd.label }}
{{ nd.sub }}
{{ rich.dg.left.title }}
{{ it }}
{{ rich.dg.right.title }}
{{ it }}
On screen — where to click

{{ rich.ui.title }}

{{ u.text }}
  1. {{ st.n }}{{ st.text }}
{{ rich.ui.title }}
{{ u.text }}
Flowchart — how it works
{{ nd.text }}
{{ nd.text }}
◇ {{ nd.text }}
Yes → {{ nd.yes }}
No → {{ nd.no }}
Syntax / Where to find it
{{ current.syntax }}
Example
{{ current.example }}
What You'll Learn — click to check off
  • {{ pt.mark }} {{ pt.text }}

Share this topic