Forum Discussion

schneiw's avatar
schneiw
Advocate IV
1 year ago
Solved

Lakehouse high CU usage, unknown source

Hi Can anyone please help me understand what is causing this high usage. The ratio between seconds and CU's consumed seems very skewed, and I do not know what is causing it. Here are some screenshot...
Lakehouse
  • schneiw's avatar
    schneiw
    1 year ago

    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.

spaceman127's avatar
spaceman127
Super User
1 year ago

Hello schneiw ,

Here you can find a Microsoft article on what all the processes are.

 

https://learn.microsoft.com/en-us/fabric/onelake/onelake-consumption

 

Another article with an example, I think you should now be able to figure out what generates these CUs.

 

https://learn.microsoft.com/en-us/fabric/onelake/onelake-capacity-consumption

 

And then here is the general description of the metric APP.

 

https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app

 

I hope the information helps you.

 

Best regards