Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hello, I have a production that I feed PowerBI via SSAS model. Recently, PowerBI refreshes started to reach 30 minutes. I want to check the duration of my daxes to shorten this time. How can I analyze the duration of my daxes?
Note: I am using Power BI web and if you have different suggestions to minimize the time, I am open to suggestions.
That's a huge question. Where is the delay--refreshing the dataset or interacting with a visual?
Some tips though, assuming it's the dataset refresh:
Are you using desktop? Is it in "import" mode? If so, try using a dataflow to do the ingest into PBI Service, then do your hardcore transforms on that copy. What happens is Power Query splits the project up to give it to multiple CPUs in a way that's not intuitive, and can easily flail the connection to the server with dozens of requests when you think you only called it once. Bringing it in to PBI first and saving it as a loaded dataflow table cuts out the chatter outside of PBI.
You can add filters as a first step to limit the amount of data being processed. Likewise incremental refresh is a thing.
Ensure query folding is being used as much as possible.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 6 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |