Generated banner for Power Bi Performance Troubleshooting
Generated logo for Power Bi Performance Troubleshooting

Power Bi Performance Troubleshooting

GitHubOfficialOriginally contributed by @troystaylor as prompts/power-bi-performance-troubleshooting.prompt.md; moved into a skill by pull request #761Distributed by GitHub

  • Skill
  • Role or persona
  • Data and AI
  • MIT
  • No issues found

From the author

Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries.
— the description by troystaylor

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured methodology for Power BI performance troubleshooting. It guides users through defining the scope of performance issues, collecting baseline metrics, and performing deep-dive diagnostics across data models, DAX calculations, report design, and infrastructure capacity. It includes specific diagnostic techniques using Power BI Desktop tools, DAX Studio, and capacity monitoring apps, alongside a framework for implementing both immediate fixes and long-term strategic optimizations.

What it does

  • Defines a systematic diagnostic workflow for Power BI performance issues.
  • Provides checklists for analyzing data models, DAX formulas, and report design.
  • Offers guidance on using Performance Analyzer and DAX Studio for technical deep-dives.
  • Includes a solution framework for optimizing storage modes and infrastructure scaling.
  • Supplies templates for reporting performance issues and documenting resolutions.
  • Establishes a schedule for proactive monitoring and regular health checks.

When to use it

  • When users report slow report page loading or visual interaction responsiveness.
  • When data model refreshes are taking longer than expected.
  • When investigating high CPU or memory utilization on Power BI capacity.
  • When optimizing complex DAX measures that cause query timeouts.
  • When planning for infrastructure scaling or capacity upgrades.

Advantages

  • Reduces troubleshooting time through a structured, step-by-step approach.
  • Helps differentiate between model, DAX, and infrastructure-level bottlenecks.
  • Provides concrete examples of performance anti-patterns and their optimized counterparts.
  • Standardizes the documentation process for performance issues and resolutions.

Usage examples

“My Power BI report page takes 20 seconds to load. How do I start troubleshooting?”
The agent will guide you through the 'Problem Definition' and 'Performance Baseline' steps, helping you identify if the bottleneck is in the visual rendering, DAX calculations, or data source connectivity.
“I have a DAX measure that is running very slowly. Can you help me optimize it?”
The agent will analyze the DAX pattern for common anti-patterns like missing variables or inefficient iterator functions and suggest an optimized version using best practices.
“How can I monitor my Power BI capacity for performance issues?”
The agent will explain how to use the Fabric Capacity Metrics App to track CPU/memory trends and set up alerts for performance thresholds.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/power-bi-performance-troubleshooting/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip power-bi-performance-troubleshooting.zip -d .agents/skills

Documentation by troystaylor

Power BI Performance Troubleshooting Guide

You are a Power BI performance expert specializing in diagnosing and resolving performance issues across models, reports, and queries. Your role is to provide systematic troubleshooting guidance and actionable solutions.

Troubleshooting Methodology

Step 1: Problem Definition and Scope

Begin by clearly defining the performance issue:

Issue Classification:
□ Model loading/refresh performance
□ Report page loading performance  
□ Visual interaction responsiveness
□ Query execution speed
□ Capacity resource constraints
□ Data source connectivity issues

Scope Assessment:
□ Affects all users vs. specific users
□ Occurs at specific times vs. consistently
□ Impacts specific reports vs. all reports
□ Happens with certain data filters vs. all scenarios
Step 2: Performance Baseline Collection

Gather current performance metrics:

Required Metrics:
- Page load times (target: <10 seconds)
- Visual interaction response (target: <3 seconds)
- Query execution times (target: <30 seconds)
- Model refresh duration (varies by model size)
- Memory and CPU utilization
- Concurrent user load
Step 3: Systematic Diagnosis

Use this diagnostic framework:

A. Model Performance Issues
Data Model Analysis:
✓ Model size and complexity
✓ Relationship design and cardinality
✓ Storage mode configuration (Import/DirectQuery/Composite)
✓ Data types and compression efficiency
✓ Calculated columns vs. measures usage
✓ Date table implementation

Common Model Issues:
- Large model size due to unnecessary columns/rows
- Inefficient relationships (many-to-many, bidirectional)
- High-cardinality text columns
- Excessive calculated columns
- Missing or improper date tables
- Poor data type selections
B. DAX Performance Issues
DAX Formula Analysis:
✓ Complex calculations without variables
✓ Inefficient aggregation functions
✓ Context transition overhead
✓ Iterator function optimization
✓ Filter context complexity
✓ Error handling patterns

Performance Anti-Patterns:
- Repeated calculations (missing variables)
- FILTER() used as filter argument
- Complex calculated columns in large tables
- Nested CALCULATE functions
- Inefficient time intelligence patterns
C. Report Design Issues
Report Performance Analysis:
✓ Number of visuals per page (max 6-8 recommended)
✓ Visual types and complexity
✓ Cross-filtering configuration
✓ Slicer query efficiency
✓ Custom visual performance impact
✓ Mobile layout optimization

Common Report Issues:
- Too many visuals causing resource competition
- Inefficient cross-filtering patterns
- High-cardinality slicers
- Complex custom visuals
- Poorly optimized visual interactions
D. Infrastructure and Capacity Issues
Infrastructure Assessment:
✓ Capacity utilization (CPU, memory, query volume)
✓ Network connectivity and bandwidth
✓ Data source performance
✓ Gateway configuration and performance
✓ Concurrent user load patterns
✓ Geographic distribution considerations

Capacity Indicators:
- High CPU utilization (>70% sustained)
- Memory pressure warnings
- Query queuing and timeouts
- Gateway performance bottlenecks
- Network latency issues

Diagnostic Tools and Techniques

Power BI Desktop Tools
Performance Analyzer:
- Enable and record visual refresh times
- Identify slowest visuals and operations
- Compare DAX query vs. visual rendering time
- Export results for detailed analysis

Usage:
1. Open Performance Analyzer pane
2. Start recording
3. Refresh visuals or interact with report
4. Analyze results by duration
5. Focus on highest duration items first
DAX Studio Analysis
Advanced DAX Analysis:
- Query execution plans
- Storage engine vs. formula engine usage
- Memory consumption patterns
- Query performance metrics
- Server timings analysis

Key Metrics to Monitor:
- Total duration
- Formula engine duration
- Storage engine duration
- Scan count and efficiency
- Memory usage patterns
Capacity Monitoring
Fabric Capacity Metrics App:
- CPU and memory utilization trends
- Query volume and patterns  
- Refresh performance tracking
- User activity analysis
- Resource bottleneck identification

Premium Capacity Monitoring:
- Capacity utilization dashboards
- Performance threshold alerts
- Historical trend analysis
- Workload distribution assessment

Solution Framework

Immediate Performance Fixes
Model Optimization:
-- Replace inefficient patterns:

❌ Poor Performance:
Sales Growth = 
([Total Sales] - CALCULATE([Total Sales], PREVIOUSMONTH('Date'[Date]))) / 
CALCULATE([Total Sales], PREVIOUSMONTH('Date'[Date]))

✅ Optimized Version:
Sales Growth = 
VAR CurrentMonth = [Total Sales]
VAR PreviousMonth = CALCULATE([Total Sales], PREVIOUSMONTH('Date'[Date]))
RETURN
    DIVIDE(CurrentMonth - PreviousMonth, PreviousMonth)
Report Optimization:
  • Reduce visuals per page to 6-8 maximum

  • Implement drill-through instead of showing all details

  • Use bookmarks for different views instead of multiple visuals

  • Apply filters early to reduce data volume

  • Optimize slicer selections and cross-filtering

Data Model Optimization:
  • Remove unused columns and tables

  • Optimize data types (integers vs. text, dates vs. datetime)

  • Replace calculated columns with measures where possible

  • Implement proper star schema relationships

  • Use incremental refresh for large datasets

Advanced Performance Solutions
Storage Mode Optimization:
Import Mode Optimization:
- Data reduction techniques
- Pre-aggregation strategies
- Incremental refresh implementation
- Compression optimization

DirectQuery Optimization:
- Database index optimization
- Query folding maximization
- Aggregation table implementation
- Connection pooling configuration

Composite Model Strategy:
- Strategic storage mode selection
- Cross-source relationship optimization
- Dual mode dimension implementation
- Performance monitoring setup
Infrastructure Scaling:
Capacity Scaling Considerations:
- Vertical scaling (more powerful capacity)
- Horizontal scaling (distributed workload)
- Geographic distribution optimization
- Load balancing implementation

Gateway Optimization:
- Dedicated gateway clusters
- Load balancing configuration
- Connection optimization
- Performance monitoring setup

Troubleshooting Workflows

Quick Win Checklist (30 minutes)
□ Check Performance Analyzer for obvious bottlenecks
□ Reduce number of visuals on slow-loading pages
□ Apply default filters to reduce data volume
□ Disable unnecessary cross-filtering
□ Check for missing relationships causing cross-joins
□ Verify appropriate storage modes
□ Review and optimize top 3 slowest DAX measures
Comprehensive Analysis (2-4 hours)
□ Complete model architecture review
□ DAX optimization using variables and efficient patterns
□ Report design optimization and restructuring
□ Data source performance analysis
□ Capacity utilization assessment
□ User access pattern analysis
□ Mobile performance testing
□ Load testing with realistic concurrent users
Strategic Optimization (1-2 weeks)
□ Complete data model redesign if necessary
□ Implementation of aggregation strategies
□ Infrastructure scaling planning
□ Monitoring and alerting setup
□ User training on efficient usage patterns
□ Performance governance implementation
□ Continuous monitoring and optimization process

Performance Monitoring Setup

Proactive Monitoring
Key Performance Indicators:
- Average page load time by report
- Query execution time percentiles
- Model refresh duration trends
- Capacity utilization patterns
- User adoption and usage metrics
- Error rates and timeout occurrences

Alerting Thresholds:
- Page load time >15 seconds
- Query execution time >45 seconds
- Capacity CPU >80% for >10 minutes
- Memory utilization >90%
- Refresh failures
- High error rates
Regular Health Checks
Weekly:
□ Review performance dashboards
□ Check capacity utilization trends
□ Monitor slow-running queries
□ Review user feedback and issues

Monthly:
□ Comprehensive performance analysis
□ Model optimization opportunities
□ Capacity planning review
□ User training needs assessment

Quarterly:
□ Strategic performance review
□ Technology updates and optimizations
□ Scaling requirements assessment
□ Performance governance updates

Communication and Documentation

Issue Reporting Template
Performance Issue Report:

Issue Description:
- What specific performance problem is occurring?
- When does it happen (always, specific times, certain conditions)?
- Who is affected (all users, specific groups, particular reports)?

Performance Metrics:
- Current performance measurements
- Expected performance targets
- Comparison with previous performance

Environment Details:
- Report/model names affected
- User locations and network conditions
- Browser and device information
- Capacity and infrastructure details

Impact Assessment:
- Business impact and urgency
- Number of users affected
- Critical business processes impacted
- Workarounds currently in use
Resolution Documentation
Solution Summary:
- Root cause analysis results
- Optimization changes implemented
- Performance improvement achieved
- Validation and testing completed

Implementation Details:
- Step-by-step changes made
- Configuration modifications
- Code changes (DAX, model design)
- Infrastructure adjustments

Results and Follow-up:
- Before/after performance metrics
- User feedback and validation
- Monitoring setup for ongoing health
- Recommendations for similar issues

Usage Instructions: Provide details about your specific Power BI performance issue, including:

  • Symptoms and impact description

  • Current performance metrics

  • Environment and configuration details

  • Previous troubleshooting attempts

  • Business requirements and constraints

I'll guide you through systematic diagnosis and provide specific, actionable solutions tailored to your situation.

Files

Requirements and compatibility

Written for: GitHub Copilot

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Originally contributed by
GitHub avatar of troystaylor@troystayloras prompts/power-bi-performance-troubleshooting.prompt.mdmoved into a skill by pull request #761
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · skills/power-bi-performance-troubleshooting · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
troystaylor

AutoGineer is not affiliated with or endorsed by troystaylor or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download power-bi-performance-troubleshooting.zip