Forum Discussion
View Nightly Refresh Busting
Hi,
We are moving into fabric from provisioned Azure SQL server (pretty much fixed price - scaled up for dataprocessing and scale down most of the day).
We process 250Gb of data over night. 2hr run time at high compute and we scale to lowest for rest of the day since its pretty quite. one in a month we had to reprocess data intraday (which is another 2 hrs)
My question is if I choose on SKU for example (F16).
- how do i view CU used for my pipeline runs with Stored procedure combination (if possible how much CU by pipeline and CU by each SP).
Hi AJAJ,
For starters, F10 does not exist. The capacities are F2, F4, F8, F16, F32, F64, F128, F256, F512, F1024, and F2048.
You can view overall capacity usage in the Cpacity Metrics app.
What is the Microsoft Fabric Capacity Metrics app? - Microsoft Fabric | Microsoft Learn
At any given timepoint, you can drill through to see what items are using the capacity at that timepoint:
Understand the metrics app timepoint page - Microsoft Fabric | Microsoft LearnIf you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
7 Replies
Hi AJAJ,
For starters, F10 does not exist. The capacities are F2, F4, F8, F16, F32, F64, F128, F256, F512, F1024, and F2048.
You can view overall capacity usage in the Cpacity Metrics app.
What is the Microsoft Fabric Capacity Metrics app? - Microsoft Fabric | Microsoft Learn
At any given timepoint, you can drill through to see what items are using the capacity at that timepoint:
Understand the metrics app timepoint page - Microsoft Fabric | Microsoft LearnIf you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
My bad. That was an example. I should have used F16 as example. For simplicy sake I guess I made it as F10.
Also keep in mind that SKU bursting comes with a 24 hour penalty. You can only scale down 24 hours after you scaled up. Which makes this unsuitable for your process.
Thats good to know. On the other hand scale up and scale down are for the existing process on Azure SQL. Once moved into fabric it will mostly likely be 24x7.
Incase I over use fabric on one day, and dont use much rest of the month, does that overage even out over the period of time?On a reservation, yes. Depending on how much and how long you overuse you may experience throttling (interactive delay/rejection or background rejection).
