Performance Analyzer in Power BI - Real Business Scenario

Scenario Mode

👤 Your Role: You are a Power BI report developer at a retail company.

📋 Request: Your manager wants you to improve the loading speed of the monthly sales dashboard because users report it is slow.

📊 Data: You have a Power BI report with multiple visuals showing monthly sales, product categories, and regional performance. The report uses several calculated measures and filters.

🎯 Deliverable: You need to use the Performance Analyzer tool in Power BI to identify which visuals or queries take the longest time to load and suggest optimizations.

Sample Data

Visual	Query Duration (ms)	Render Duration (ms)	Total Duration (ms)
Monthly Sales Line Chart	1200	800	2000
Category Sales Bar Chart	900	700	1600
Region Sales Map	1500	1000	2500
Top Products Table	600	400	1000
Sales KPI Card	300	200	500

1

Step 1: Open your Power BI report and go to the View tab. Enable the Performance Analyzer pane.

Click 'Start Recording' in Performance Analyzer before interacting with the report visuals.

Expected Result

Performance Analyzer starts capturing the time taken by each visual to query and render.

2

Step 2: Refresh the report page or interact with the visuals to capture their performance data.

Observe the list of visuals with their Query Duration, Render Duration, and Total Duration in Performance Analyzer.

Expected Result

You see the following durations: Region Sales Map (2500 ms), Monthly Sales Line Chart (2000 ms), Category Sales Bar Chart (1600 ms), Top Products Table (1000 ms), Sales KPI Card (500 ms).

3

Step 3: Identify the visual with the highest total duration to focus optimization efforts.

Region Sales Map has the highest total duration of 2500 ms.

Expected Result

You confirm that the Region Sales Map is the slowest visual.

4

Step 4: Export the DAX query for the slowest visual from Performance Analyzer to analyze its complexity.

Click 'Copy Query' for the Region Sales Map visual and paste it into DAX Studio or Power BI Advanced Editor.

Expected Result

You get the DAX query used by the Region Sales Map visual.

5

Step 5: Review the DAX query and data model to find possible optimizations such as reducing calculated columns, simplifying measures, or limiting data volume.

Check if the Region Sales Map uses complex measures or large data sets that can be filtered or aggregated.

Expected Result

You find that the map uses a complex measure with multiple filters and a large dataset.

6

Step 6: Apply optimizations such as creating summary tables, simplifying measures, or adding report-level filters to reduce data load.

Modify the measure to use pre-aggregated data or add a filter to limit data to the last 12 months.

Expected Result

The Region Sales Map visual query duration reduces significantly.

7

Step 7: Re-run Performance Analyzer to verify improvements after optimization.

Start recording again and refresh the report page.

Expected Result

Region Sales Map total duration decreases from 2500 ms to under 1500 ms.

Final Result

Performance Analyzer Report

Visual                  | Query (ms) | Render (ms) | Total (ms)
--------------------------------------------------------------
Region Sales Map        | 900        | 500         | 1400
Monthly Sales Line Chart| 1200       | 800         | 2000
Category Sales Bar Chart| 900        | 700         | 1600
Top Products Table      | 600        | 400         | 1000
Sales KPI Card          | 300        | 200         | 500

Optimization Focus: Region Sales Map visual
Total duration reduced by 44% after optimization.

✓The Region Sales Map visual was the slowest, taking 2500 ms initially.

✓After optimization, its total duration dropped to 1400 ms, improving report responsiveness.

✓Using Performance Analyzer helps pinpoint slow visuals and guides targeted improvements.

✓Simplifying complex measures and limiting data volume are effective optimization strategies.

Bonus Challenge

Use Performance Analyzer to compare performance before and after applying a slicer filter for a specific region. Analyze how filtering affects query and render times.

Show Hint

Record performance with no filters, then apply the slicer and record again. Compare durations to see if filtering improves or worsens performance.