Fabric compute capacity exceeded its limits. How to know how much CU each dataflowgen2 consumes

[je777999]

Our dataflowgen2 got Failed status after exceeding the Fabric compute capacity limit

At the moment, I'm trying to access Fabric Capacity Metrics to see if it can be viewed there but cant open it as well with message "Unable to load model due to reaching capacity limits"

- How to know how much CU each activity(dataflowgen2,notebook,etc) in a datapipeline consume so we can avoid hitting the CU limit?

- Do we have other way to view fabric capacity metrics?

[je777999]

Hoping to get clear exact answer to each of my question.

[je777999]

Hi v-cboorla-msft,

Thank you for replying. I have further questions related to restarting and capacity.

How to restart the Power BI Service(you mean Fabric)?

Regarding capacity, hoping you can answer each of my questions below:

	Questions	Answer
1	Where and how to check how much CU we consume per dataflowgen2, datapipeline, more
2	Sample we have F2, how much CU we can use per minute and per hour without reaching its limit?
3	Whats the exact maximum carry forward for SKU F2 and other SKU?
4	how long exactly an SKU will be at frozen if ever we reached the maximum carry forward limit?
5	If we purchased F2 Pay-as-you-go, are we only billed when we consumed CU?	Yes 😃
6	Is there a lock in period for Pay-as-you-go?	No 😃
7	Is there a lock in period for Reservation?	Yes =(
8	Can we  have 10 Pay-as-you-go SKU F2, and if ever one of it get frozen, while waiting for it to refresh from being frozen, can we swap it with other SKU F2, so we can continue using our workspace?

[v-cboorla-msft]

Hi @je777999 

Apologies for the delay in response.

Below are the insights which might help you.

1. Where and how to check how much CU we consume per dataflowgen2, datapipeline, more

• You can use the Microsoft Fabric Capacity Metrics app. This app provides an overview of your capacity’s performance and usage, and allows you to filter by item, operation, user, and date.
• For more details on how CU consumption is calculated for different Fabric operations, you can refer to the Fabric operations document.

2. Sample we have F2, how much CU we can use per minute and per hour without reaching its limit?

• F2 SKU has a baseline of 2 Capacity Units (CU) and a burstable scale factor of 32x. This means that you can use up to 64 CU per minute and 3,840 CU per hour without reaching the limit of your F2 SKU.

3. Whats the exact maximum carry forward for SKU F2 and other SKU?

• The exact maximum carry forward for SKU F2 and other SKU in Microsoft Fabric depends on the type of billing plan you choose.
• For example, if you purchase an F2 SKU with pay-as-you-go plan, you can use up to 2 CUs per minute, and carry forward up to 2 CUs to the next minute. If you purchase an F2 SKU with reservation plan, you can use up to 2 CUs per minute, and carry forward up to 2 CUs to the next minute, but you cannot change your SKU size until the end of the reservation term.

4. How long exactly an SKU will be at frozen if ever we reached the maximum carry forward limit?

• If the carry forward reaches a full hour, interactive requests are rejected, but background scheduled operations continue to run. If the capacity accumulates a full 24 hours of carry forward, the entire capacity is frozen until the carry forward is paid off.
• If you need to pay down your carry forward faster, you can increase your SKU size temporarily to generate more idle capacity that is applied to your carry forward. For more details please refer : Throttle triggers and throttle stages 

8. Can we  have 10 Pay-as-you-go SKU F2, and if ever one of it get frozen, while waiting for it to refresh from being frozen, can we swap it with other SKU F2, so we can continue using our workspace?

• Yes, you can have 10 Pay-as-you-go SKU F2, and if ever one of them gets frozen, you can swap it with another SKU F2, as long as you have enough CUs available in your tenant. Swapping SKUs is a new feature that was introduced in the October 2023 update of Microsoft Fabric.

I hope this informations helps. Please do let us know if you have any further questions.

Thanks

[v-cboorla-msft]

Hi @je777999 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond back with the more details and we will try to help.

Thanks

[je777999 · Accepted solution]

Hi @v-cboorla-msft 

Thank you for the valuable information.

To add more information, CU is per second. Like F8 has 8 CU per second, F4 has 4 CU per second, and so on. "https://learn.microsoft.com/en-us/fabric/data-warehouse/burstable-capacity"

and if it is CU per second, these table below is a good guide to know how much CU  can be used per second to per day

Just be sure to take note of Throttling and not consume 24 hour worth of CU to not get your SKU frozen. https://learn.microsoft.com/en-us/fabric/data-warehouse/compute-capacity-smoothing-throttling#thrott...

We tried F4 for testing and found our CU consumption can deplete it (carry forward included) around 12 hours. 😃

[v-cboorla-msft]

Hi @je777999 

Thanks for using Microsoft Fabric Community.

Apologies for the issue that you are facing here.

Try restarting the Power BI Service and check whether your issue got resolved. Otherwise the issue can be due to throtlling.

Throttling occurs when a tenant’s capacity consumes more capacity resources than it has purchased. Too much throttling can result in a degraded end-user experience. A Fabric tenant can create multiple capacities and assign workspaces to a specific capacity for billing and sizing.

Throttling is applied at the capacity level, meaning that while one capacity, or set of workspaces, may be experiencing reduced performance due to being overloaded, other capacities may continue running normally. 

For more details please refer Link.

If the issue still persists please do let us know.

I hope this helps.