Troubleshooting Power BI Report Performance
summary
Demonstrates using the Performance Analyzer to record interactions, exporting its logs, and pairing that with DAX Studio server timings to spot FE/SE splits; shows a 95 million‑row NYC bikes dataset and a map with ~1,200 bubbles that causes 1–2s visual rendering delays. Uses VertiPaq Analyzer to find two datetime columns inflating the model and shows a star‑schema refactor that shrinks a model from ~960 MB to ~160 MB. Uses Tabular Editor best‑practice rules; calculated columns and auto date tables prove costly.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:52Who am I
- 2:05What is this session about
- 3:26Why should we troubleshoot
- 7:04What is noisy neighbours
- 8:24Premium capacity
- 16:00Performance Analyzer Pane
- 17:02Why Im Landing on a Blank Page
- 17:47Open Performance Analyzer Pane
- 18:14Analysis
- 22:59Query Cache
- 28:11Metadata
- 34:16Best Practice Analyzer
- 36:27Tools
- 37:09Golden Rules
- 38:15Data Types
- 40:33Modeling
related talks
50mTroubleshooting Power BI Reports
50mThe Path to Success with Power BI: Best Practices
48mCombine Power BI with External Tools
46mVisualizing Data for Non-Data Experts: Making Reports Accessible to All
51mPower BI Composite and Hybrid Models
43mBecome a Power BI Data Modeling Wizard using Tabular Editor 3
54mData Visualization with Power View and the Tabular Model
51mOptimising DAX fusion - Power BI