Forum Discussion
Lakehouse high CU usage, unknown source
Support finally got back to me with this reply. They admitted to it being a backend Microsoft issue, but no word on how and if they would be fixing it or if I would be reinbursed the lost CU's. The abbreviated 'DMS' is for Data Movement Services:
The increased CU usage was attributed to a disabled file system (FS) on the DMS side, which resulted in a significant number of “GetBlobProperties” API calls from DMS to the One Lake Client (OLC). This led to the observed spike in CU usage. After the FS was re-enabled on July 29th, CU usage decreased accordingly.
The spike occurred on 07/18 and subsided on 07/29, aligning with the period when the FS was disabled and subsequently re-enabled on the DMS side, which reduced the number of calls from DMS to OLC.
I have done nothing to or with (i.e. no pipeline, notebooks queries etc reading or writing) these lakehouses today, yet the comsumed CU's is exceptionally high, I would have expected them to be zero.
Since you have a Pro license you should open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Thanks, I was trying in the wrong place for support ticket! I did successfully log a ticket and will update this post with Microsoft's findings.
I checked it on a lakehouse that is practically not used at all. The CU is virtually zero.
I think opening a ticket with MS is also the right way to go.
Best regards
I am having the same issue on the same timeline. It is not resolved.
The dramatic increase for me came from BCDR operations on lakehouses with shortcuts. These did not used get charged for BCDR before Saturday and now we are seeing a dramatic increase in CU usage. Nearly a quarter of our capacity is committed to these new BCDR operations as of Saturday.
I had a call with support today, they are investigating and I will update their findings. The support tech said they had never seen spikes like this before so hopefully they can correlate to a change that they made to the backend.
