Forum Discussion
eventstream consumption (CU%)
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:
- lbendlin1 year ago
Super User
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.
- frithjof_v1 year ago
Community Champion
If we cancel a recurring activity, the impact of the smoothed CU consumption (red bars in my graphic below) will start to decrease almost immediately, as the smoothing period for the previous runs completes one by one.
The smoothed CU consumption stemming from the recurring activity will be fully reduced to zero 24 hours after cancelling the recurring activity.
- joakimfenno1 year ago
Helper V
thanks for clarifying
I dont see that behaviour - it seems like the eventstream consumes a F4 capacity just by being active (and not processing any data)