March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hi Fabric Community,
I have a question which I have not come across, hopefully I'm not asking a question that have already been answered.
My concern with our Fabric capacity right now is the amount of Background Compute Units we are consuming. I have several dataflows refreshing 2 times per day. The total time for refreshes for the entire day takes 35 minutes (so about 15-20 minutes in the morning and 15-20 min mid-afternoon).
When I look at the Fabric Metrics Usage:
I can see that the primary usage for us is background. How is it possible to reduce or turn this off? This accounts for well over 95% of our Fabric costs.
For example, I don't understand how we are incurring these costs even during nighttime when we are not doing anything with reporting, refreshing dataflows, etc.
We are at the trial capacity right now
Looking forward to your guidance and help.
Brds,
Hi @abaOnego
I have found the following for you, maybe it will help you:
Understand your Fabric capacity throttling - Microsoft Fabric | Microsoft Learn
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
3 | |
2 | |
2 | |
1 | |
1 |