At some point Microsoft started graphing "CU" in the capacity dashboard instead of CPU. Their goal is to promote this concept of "carry forward" and "smoothing". Customers are regularly borrowing from future capacity, and the Power BI service is slowly becoming a payday lender, in addition to a reporting service. The claim is that it is easier to manage, but that is not my experience so far.
The CU changes have made this environment very troublesome to manage. If we want to actually find *actionable* ways to fix specific problems, we need to be able to see more detail. Eg. we need the CPU impact when it is *incurred*, rather then the smoothed version. Instead, of managing CPU as it is incurred, Microsoft appears to be reporting a version of the CPU wherein smoothing-accruals are used and the resulting CPU penalties are spread over a long period of time.
Consider the CPU of background operations, based on the following chart:
![dbeavon3_0-1715005601498.png dbeavon3_0-1715005601498.png]()
This chart is almost useless where background CPU is concerned. As you can see, our background consumption is growing out of control (around 30% of total available CPU for the day). But the impact can't be easily managed. We can't isolate whether the background is happening off-hours or not. We can't see where the CPU is incurred. All we have to look at is a big blue bar at the bottom of our utilization graph, and it rises on a daily basis.
We can drill through to timepoint detail, but that loses our ability to visualize usage-over-time. The background operations in that screen are reported in a disorganized way. It doesn't clearly indicate what periods are incurring the most CPU for background operations, so that it can be minimized.
![dbeavon3_1-1715006150367.png dbeavon3_1-1715006150367.png]()
My question is how do we visualize the background CPU in a way that tells us when the CPU cost are *incurred*. That would be far more actionalbe than visualizing the "smoothed" version of this data.
https://learn.microsoft.com/en-us/power-bi/enterprise/service-premium-smoothing
I find it really bothersome that Microsoft pushed these carry-forward and smoothing concepts as far as they did. It is not likely that this was done based on customer requirements. It seems these changes make it harder than ever for customers to try and manage their CPU usage and, by extension, costs.