Forum Discussion
Fabric Performance Extraction
- 6 months ago
Hi Rajkumar106,
This is because of the smoothing that Fabric does to CU usage. Background operations are smoothed over a 24 hour period.
Understand your Fabric capacity throttling - Microsoft Fabric | Microsoft Learn
So even though the process stopped, the compute it used is smoothed over a longer period.
To directly answer your questions:
1: yes
2: No
3: you should use all timepoints as actual utilization.
- 6 months ago
Hi Rajkumar106,
For background operations, that is correct. All background operations are smoothed over a 24 hour window.
Interactive operations are a little more fun, the smoothing window for them is at least 5 minutes, but can be longer depending on what type of operation and how intensive it is.
Just to confirm our understanding: since Fabric smooths CU usage over 24 hours, the same operation appears across multiple timepoints even after it stops. Based on this, should we consider all these timepoints as actual utilization?
For our downscale recommendation logic, should these smoothed timepoints also be treated as utilized periods, meaning they are not safe for downscaling?