The Premium Capacity Metrics app gives you a lot of information about CPU usage across your Premium capacities. Power BI Premium gen2 works differently (as explained in detail here and here): you no longer have a fixed set of resources available, but if you use more CPU than your capacity allows you will either pay extra (if you enable autoscale) or get throttled. So why is CPU Time so important? In Power BI Premium gen1 you have a fixed set of resources that all your queries and refreshes compete for if you try to use more CPU than you have available then performance suffers. In fact, in the past, CPU Time didn’t even return accurate values so it wasn’t useful – although that changed recently. The same data is available in Log Analytics, albeit with slightly different column names: the EventText holds the query text, DurationMs has the duration and CpuTimeMs has the CPU time:Īs I said, it’s the duration that, traditionally, you would have wanted to reduce. The Command End event gives you similar information for refreshes:
The TextData column gives the query text, the Duration column shows the amount of time the query took to run in milliseconds and the CPUTime column is a representation of the amount of CPU resources used by the query: However, if you are using Power BI Premium you also need to think about reducing the amount of CPU used by a query or refresh as well, and in this post I’ll explain why.įirst of all, what are the metrics I’m talking about? For query performance tuning, if you connect SQL Server Profiler to Power BI Desktop or the Power BI Service (as described here for example) and look at the Query End event you can see all the DAX queries executed when a report is rendered. When you tune a Power BI report or dataset refresh your first job is to make it run faster – users hate slow reports and late data.
0 kommentar(er)
