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.
Thank you for your links to help me understand. Its still not that clear what is causing this. From the documentation its based on "operations", which are suppoed to be 104 CUs per 10000:
Using the FAUM app, I can see then how many operations are being perfomred on a given day per Lakehouse. For example most of these lakehouses are averaging around 2900 operations for 3 seconds, yet the total CU's are vastly different for some . Something isnt adding up here.....