How to Use Performance Analyzer in Power BI

A slow-running Power BI report can be incredibly frustrating for everyone involved. As a creator, you’ve spent hours building what you thought was a masterpiece, only to see users annoyed by spinners and laggy visuals. Users just want answers, and waiting 30 seconds for a chart to update feels like an eternity.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

If your Power BI dashboards are feeling sluggish, the Performance Analyzer is your secret weapon. This built-in tool is designed to help you diagnose exactly what’s causing the slowdowns, giving you a clear roadmap for what to fix. This guide will walk you through, step-by-step, how to use it to turn your sluggish reports into lightning-fast tools for analysis.

What is the Performance Analyzer and Why Should You Care?

The Performance Analyzer is a feature within Power BI Desktop that records and displays the time it takes for each element in your report to perform its operations. Think of it as a doctor’s diagnostic tool for your dashboard. When you interact with a slicer or filter, the Analyzer logs how long each visual takes to run its underlying calculations (the DAX query) and how long it takes to actually draw the chart on the screen (the visual display).

Why is this so important? Because speed matters. A report that loads quickly feels reliable and encourages exploration. A slow report does the opposite. It leads to user frustration, lower adoption rates, and a breakdown in trust in the data. You can build the most brilliant data model in the world, but if the report is too slow to use, nobody will get value from it. The Performance Analyzer is your first and best line of defense against creating reports that people would rather avoid using.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Getting Started: Your First Performance Analysis

Getting the analyzer up and running is straightforward. It’s built directly into Power BI Desktop, so there’s nothing to install. Let’s walk through the process of conducting your first analysis.

Step 1: Launch the Performance Analyzer

First, open your Power BI report in Power BI Desktop. Once it’s loaded, navigate to the View tab in the main ribbon. In the "Show panes" section, you’ll see a checkbox labeled Performance Analyzer. Click it.

A new pane will appear on the right side of your screen, right next to the Visualizations and Fields panes. It's a simple-looking interface with just a few buttons, but don’t let its simplicity fool you.

Step 2: Start Recording Your Actions

Inside the Performance Analyzer pane, you’ll see a prominent green button labeled Start recording. Click this button to begin your analysis session. From this moment on, Power BI will log the performance of every action you take within your report.

Now, interact with your report just like a user would. Here are a few common actions to try:

• Click on a slicer to filter the page.
• Select a data point in one chart to see how it cross-filters other visuals.
• Switch between different pages in your report.
• Click the "Refresh visuals" button within the Performance Analyzer pane itself to simulate a user landing on the page for the first time.

As you perform these actions, you’ll see the Performance Analyzer pane populate with entries. Each visual affected by your action will get its own entry, complete with a breakdown of its processing time.

Once you’ve tested the main interactions on your report page, click the Stop button to end the recording session.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Decoding the Results: What Do These Numbers Mean?

After stopping your recording, you’ll have a list of all your report elements and their corresponding processing times. Each entry can be expanded to show a detailed breakdown, but the main grid gives you the most critical information sorted by longest total duration. Let’s break down what each of the time measurement columns means:

• DAX query: This is the time it took Power BI's Analysis Services engine to process the DAX (Data Analysis Expressions) formulas required for the visual. A long duration here almost always points to an inefficient measure or a complex data model that needs optimization. This is often the biggest bottleneck in slow reports.
• Visual display: This measures how long it took for the visual itself to be drawn on the screen. It includes time for rendering, retrieving images, or mapping geocoding data. High times here often mean the visual is trying to display too many data points (e.g., a table with 50,000 rows or a scatter plot with thousands of markers).
• Other: This is a catch-all category for time the visual spent waiting for other things to complete. Often, a high "Other" time means the visual was waiting on another, much slower operation to finish (like a different visual finishing its long DAX query) or performing other small background tasks.
• Duration (ms): This is the total time for the operation, essentially summing the three categories above. The Performance Analyzer automatically sorts your results by this column in descending order, putting your biggest performance problems right at the top.

By understanding these four metrics, you can quickly diagnose the root cause of the slowdown. A high DAX query time tells you to look at your data model and formulas. A high Visual display time tells you to simplify the visual itself.

From Analysis to Action: Fixing Common Performance Killers

Identifying the problem is only half the battle. Now it’s time to fix it. Here are some of the most common issues uncovered by the Performance Analyzer and how you can resolve them.

Problem #1: Slow DAX Queries

If you see DAX query times stretching into multiple seconds, it's time to optimize your code and data model. Inefficient DAX can bring even the most powerful machine to its knees.

Actionable Solutions:

• Use variables in your measures: Variables (using the VAR statement) are a DAX superhero. They store the result of a calculation, so Power BI doesn't have to compute the same logic multiple times within a single measure. This is an easy win for optimizing complex formulas.
• Optimize your data model: A clean, well-structured data model is the foundation of a fast report. Follow best practices like the star schema, where you have a central fact table (like "Sales") connected to multiple dimension tables (like "Date," "Product," "Customer"). This structure is much more efficient for the Power BI engine to process than a single, wide, flat table. Also, hide columns in the data model view that aren’t needed for reporting to reduce the model's memory footprint.
• Analyze the query with DAX Studio: For truly complex DAX mysteries, you can copy the query directly from the Performance Analyzer. Just click on the visual's entry and select "Copy query." You can then paste this into a free, external tool called DAX Studio. This tool can run the query and give you an incredibly detailed performance breakdown, showing exactly where the engine is spending its time.

Problem #2: Long Visual Display Times

Sometimes the DAX is fast, but the visual takes forever to appear. This usually means you’re asking Power BI to draw too many things on the screen.

Actionable Solutions:

• Reduce data points: Do you really need to display a table with 200,000 rows? Probably not. A user can't possibly analyze that much data at once. Consider summarizing your data or displaying only the "Top N" items. For charts like line or scatter plots, having thousands of data points forces the renderer to work unnecessarily hard. Find ways to aggregate or filter the data presented.
• Limit the number of visuals on a single page: A report page packed with 40 different visuals will load slowly, no matter how optimized each individual visual is. Every element consumes resources. Consolidate information, use tooltips to show secondary information, and focus each report page on answering a specific set of questions.
• Be cautious with custom visuals: Custom visuals from the AppSource marketplace can be fantastic, but not all are created equal. Some are less performance-optimized than the standard, built-in visuals. If you suspect a custom visual is the culprit, the Performance Analyzer is the perfect tool to test it against a standard alternative.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Problem #3: The Sneaky "Other" Category

A high "Other" duration can be confusing, but it usually signifies a cascading failure. One slow visual can hold up multiple other visuals on the page, causing their "Other" time to spike as they wait for the bottleneck to be resolved.

Actionable Solutions:

• Focus on the biggest offenders first: Ignore the "Other" column initially. Sort your analyzer results by total duration and tackle the visuals with the highest "DAX query" and "Visual display" times. In most cases, once you fix the primary bottleneck, the "Other" times for the remaining visuals will dramatically decrease or disappear entirely.

Advanced Tips for Performance Tuning

Once you’ve mastered the basics, you can use the Performance Analyzer for more advanced tuning.

• Export performance data to track improvements: The analyzer has an “Export” button that saves the recording session as a JSON file. This is incredibly useful for documenting your progress. Run a recording before you make any changes and export it. Then, after applying your optimizations, run another recording and export it again. You can then compare the two files to precisely quantify the performance gains and show colleagues or clients the impact of your work.
• Analyze full-page load times: Often, the most important metric is how long a page takes to load when a user first navigates to it. Use the Refresh visuals button inside the Performance Analyzer pane to trigger a refresh of every visual on the page simultaneously. This gives you a holistic view of the cumulative load time and helps you identify which visuals are a drag on the initial user experience.

Final Thoughts

Optimizing Power BI reports may seem like a dark art, but the Performance Analyzer demystifies the process entirely. By systematically recording user interactions, interpreting the results for DAX query and visual display times, and applying targeted fixes, you can transform slow, cumbersome reports into fast, responsive tools that your users will love.

All this manual work to tune, rebuild, and optimize reports is why they can become such a time sink. Hours spent wrestling with DAX or reconfiguring visuals is time you're not spending on getting actual insights from your data. We built Graphed to short-circuit this entire cycle. Rather than connecting your data to a complex BI tool that requires constant tuning, we let you connect your data sources in one place and simply ask questions. You can ask for a dashboard or a specific chart in plain English, and our AI builds it in seconds, saving you from the slow, manual process of traditional report building.