Forum Discussion
eventstream consumption (CU%)
My fabric run out of capacity today
"Unable to complete the action because your organization's Fabric compute capacity has exceeded its limits. Try again later"
efter some troubleshooting and using teh fabric capacity metric app I understand that it is my event streams (2) that are the biggest consumers
The eventstream read messages from kafka.
I turned kafka (or the app that connect kafka to evenstream) off and expected the eventstream CU usage to go down but it did not go down at all
I have verified that no messages are processed through the eventstream
Can anyone explain this to me?
9 Replies
CUs are "smoothed out" over a 24 hr period. That means when you switch the consumer off your capacity will continue to be overloaded for many more hours.
What can you do about it? Move all workloads to a different capacity. Don't have one? Then you are stuck.
Not all the visuals in the Capacity metrics app show smoothed CU consumption. Some visuals show the raw, unsmoothed CU consumption aggregated to a daily or hourly granularity.
Here is a great video about how to interpret the Capacity Metrics App:
I have waited more than 24 hours
It really seems like the event stream consumes a lot CU even when its not receiving any data
Even with smoothing, you would see the consumption starting to decrease "immediately" if you have already had stable operation for more than a full 24 hours prior to shutting off the operation.
The smoothed consumption would gradually move towards zero, and would reach zero 24 hours after the operation was stopped.
I recommend this video about the Capacity metrics app, it made the Capacity metrics app a lot more useful to me after watching it: https://youtu.be/EuBA5iK1BiA?si=Ibnz7o22ePEk-WMR
Here is some information about Event Streams capacity consumption:
Microsoft Fabric event streams capacity consumption - Microsoft Fabric | Microsoft Learn
It seems strange that your Event Stream is still consuming CUs if there has been no data movement for more than 2 hours:
Even with smoothing, you would see the consumption starting to decrease "immediately" if you have already had stable operation for more than a full 24 hours prior to shutting off the operation.That's a fallacy. The smoothing is even over the 24 hr period for each consumption event. There's nothing "decreasing immediately", especially not when you continue to have new consumption events.
Thanks for the heads up, please vote (1) Smoothing is not Smoothies - Microsoft Fabric Community
