Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hi folks,
I have a Power BI report that generates significant CPU consumption and it accounts for a big portion of the whole premium capacity consumption. As a result, the capacity becomes throttled. What we know is most of this consumption comes from interactive (query) operations. For this reason, we want to optimize the report.
However, it is a huge report that contains many pages, measures and visuals. It is difficult to assess which interactions specifically account for the majority of the CPU consumption. I already know which visuals have the highest loading time, but how do I know, for exmaple, if these visuals actually account for the high consumption? I can also have the number of views per page with the usage metrics report which could help, but I am wondering if a better approach/tool exsists.
Is there a way to find out which specific query operations generate how much of the CPU consumption? Can Capacity Metrics App, for example, provide this info?
Any ideas/solutions are welcome!
The obvious but very expensive answer is to use Azure Log Analytics on the workspace that you suspect of hosting the offending queries.
Capacity Metrics doesn't go down to query level.
Try to isolate the user causing the CUs and watch them use the report.
@lbendlin, thanks for your input.
Do you mind explaining why the Azure Log Analytics solution is so expensive and how would that work?
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
34 | |
30 | |
18 | |
12 | |
8 |
User | Count |
---|---|
50 | |
35 | |
30 | |
14 | |
12 |