Forum Discussion
CUs calculation
Fabric is allowed to burst. It means it can consume more than the CU capacity for a time period, and then smooth that CU (s) usage over 24 hours (for background operations).
The duration of 61 300 seconds is roughly 17 hours. In this period, it has on average consumed resources as if it has 23 CUs, but it only has 8 CUs.
Now it will try to smooth this out over a future 24 hours window.
However this has probably been too much (too high CU over too long time), so it enters throttling. Consuming on average 23 CUs for 17 hours in a day will not be sustainable on an F8.
But using 23 CUs on average for 8 hours a day could in theory be sustainable on an F8, due to the 24 hour smoothing:
23CU/8CU * 8h/24h < 100%
But 23 CUs for 17 hours becomes too much for it:
23 CU / 8 CU * 17 h / 24 h = 203.6 %
Here's the best video I have seen about the Fabric Capacity Metrics App:
Fabric is allowed to burst. It means it can consume more than the CU capacity for a time period, and then smooth that CU (s) usage over 24 hours (for background operations).
The duration of 61 300 seconds is roughly 17 hours. In this period, it has on average consumed resources as if it has 23 CUs, but it only has 8 CUs.
Now it will try to smooth this out over a future 24 hours window.
However this has probably been too much (too high CU over too long time), so it enters throttling. Consuming on average 23 CUs for 17 hours in a day will not be sustainable on an F8.
But using 23 CUs on average for 8 hours a day could in theory be sustainable on an F8, due to the 24 hour smoothing:
23CU/8CU * 8h/24h < 100%
But 23 CUs for 17 hours becomes too much for it:
23 CU / 8 CU * 17 h / 24 h = 203.6 %
Here's the best video I have seen about the Fabric Capacity Metrics App: