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.

Practice

1. What is the main purpose of the Performance Analyzer in Power BI?

easy

A. To create new visuals automatically

B. To share reports with other users

C. To clean and transform data before loading

D. To find which visuals or queries are slow in a report

Solution

1. Step 1: Understand Performance Analyzer's role

   Performance Analyzer tracks how long each visual or query takes to run in a report.

2. Step 2: Identify its main use

   It helps find slow parts so you can improve report speed.

3. Final Answer:

   To find which visuals or queries are slow in a report -> Option D

4. Quick Check:

   Performance Analyzer = Find slow visuals [OK]

Hint: Performance Analyzer shows slow visuals to fix [OK]

Common Mistakes:

• Thinking it creates visuals
• Confusing it with data cleaning tools
• Assuming it shares reports

2. Which of the following is the correct way to start recording in Performance Analyzer?

easy

A. Click 'Start Recording' button before interacting with visuals

B. Right-click on a visual and select 'Record Performance'

C. Open the Data view and click 'Record'

D. Use the DAX formula ANALYZE() in a measure

Solution

1. Step 1: Recall Performance Analyzer usage

   You start recording by clicking the 'Start Recording' button in the Performance Analyzer pane.

2. Step 2: Check other options

   Right-click menus or DAX formulas do not start recording; Data view is unrelated.

3. Final Answer:

   Click 'Start Recording' button before interacting with visuals -> Option A

4. Quick Check:

   Start Recording button = Begin analysis [OK]

Hint: Always click 'Start Recording' first in Performance Analyzer [OK]

Common Mistakes:

• Trying to record from right-click menu
• Looking for recording in Data view
• Using DAX formulas to record

3. You used Performance Analyzer and saw these timings for a visual:
Query Duration: 1200 ms
Visual Display: 300 ms
What is the total time taken to render this visual?

medium

A. 1500 ms

B. 900 ms

C. 1200 ms

D. 300 ms

Solution

1. Step 1: Understand timing components

   Total time = Query Duration + Visual Display time.

2. Step 2: Add the times

   1200 ms + 300 ms = 1500 ms total.

3. Final Answer:

   1500 ms -> Option A

4. Quick Check:

   1200 + 300 = 1500 ms [OK]

Hint: Add query and display times for total visual time [OK]

Common Mistakes:

• Using only query duration
• Using only visual display time
• Subtracting times instead of adding

4. You started Performance Analyzer but it shows zero time for all visuals even after interacting. What is the likely problem?

medium

A. You need to refresh the data source first

B. Your report has no visuals

C. You forgot to click 'Start Recording' before testing

D. Performance Analyzer only works in Power Query Editor

Solution

1. Step 1: Check recording status

   If no times appear, recording was likely not started.

2. Step 2: Evaluate other options

   Reports always have visuals; Performance Analyzer works in report view; refreshing data is unrelated.

3. Final Answer:

   You forgot to click 'Start Recording' before testing -> Option C

4. Quick Check:

   No recording = zero times [OK]

Hint: Always start recording before interacting with visuals [OK]

Common Mistakes:

• Assuming no visuals means no data
• Thinking it works in Power Query Editor
• Believing data refresh affects Performance Analyzer

5. You notice a visual takes 5000 ms to load, mostly in 'DAX Query' time. What is the best way to improve performance using Performance Analyzer insights?

hard

A. Disable Performance Analyzer to speed up visuals

B. Optimize the DAX measure or reduce data complexity

C. Increase the report page size to load faster

D. Add more visuals to balance the load

Solution

1. Step 1: Interpret DAX Query time meaning

   High DAX Query time means the measure or data model is slow.

2. Step 2: Choose optimization approach

   Improving DAX formulas or simplifying data reduces query time and speeds visuals.

3. Step 3: Evaluate other options

   Increasing page size or adding visuals won't help; disabling Performance Analyzer doesn't affect performance.

4. Final Answer:

   Optimize the DAX measure or reduce data complexity -> Option B

5. Quick Check:

   High DAX time = optimize DAX [OK]

Hint: Fix slow DAX queries to speed visuals [OK]

Common Mistakes:

• Thinking more visuals improve speed
• Disabling Performance Analyzer helps performance
• Changing page size affects query time