Fabric SKU Calculator : (How to Calculate No of Batch Cycle?)

[Debadutta]

I'm seeking clarification on how batch cycles are calculated in the Microsoft Fabric Capacity Calculator.

In our current setup, one of our pipelines (NRT) runs every 15 minutes, resulting in 96 runs per day. However, I noticed that the calculator still treats this as only 1 batch cycle.

From what I understand:

• All 96 runs follow the same data processing logic.

• It’s a continuous ingestion process, not 96 distinct end-to-end flows.

• There’s no branching logic or different processing pathways across the runs.

My question:
In such cases, should we input “1” or “96” for batch cycles in the calculator?

If the logic and transformation remain constant across all runs, does it still count as 1 batch cycle despite the high execution frequency?

Or
Should we only increment the batch cycle count if there are multiple, distinct pipelines or processing variations?

[v-menakakota · Accepted solution]

Hi @Debadutta ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.

Please go through the Microsoft Fabric updates blog which helps in the resolving the issue.
Mastering SKU Estimations with the Microsoft Fabric SKU Estimator | Microsoft Fabric Blog | Microsof...

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

[rayalwarkamal · Accepted solution]

Hi @Debadutta ,
From what I’ve learned (and confirmed through Microsoft’s documentation), the "Batch cycles per day" field in the Fabric Capacity Calculator isn’t about how often a pipeline runs, it’s about how many unique workflows you have.

In your case:

• Your pipeline runs every 15 minutes (so 96 times a day)

• Each run follows the same logic no branching or different processing steps

Because of that, even though it runs frequently, it’s still considered just one batch cycle in the calculator. The calculator is really measuring the complexity and number of different jobs, not how many times one job runs.

You’d only increase the batch cycle count if:

• You’re running multiple pipelines with different logic

• You have workflows with significantly different processing paths

• Or you're handling very different types of data in each job

Here’s the reference from Microsoft’s official documentation:
👉 https://learn.microsoft.com/en-us/fabric/enterprise/fabric-sku-estimator

[v-menakakota]

Hi  @Debadutta ,
 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily.

Best Regards, 
Menaka.
Community Support Team 

[v-menakakota]

Hi @Debadutta ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you

[v-menakakota]

Hi @Debadutta ,

Thanks for reaching out to the Microsoft fabric community forum. 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution so that other community members can find it easily. 

Best Regards, 
Menaka.
Community Support Team  

[jennratten]

Hello @Debadatta - The number of daily batch cycles should be entered as 'how often you run full end-to-end processing. If you have many load schedules for individual tables, consider this as a single batch window.'

[v-menakakota · Accepted solution]

Hi @Debadutta ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.

Please go through the Microsoft Fabric updates blog which helps in the resolving the issue.
Mastering SKU Estimations with the Microsoft Fabric SKU Estimator | Microsoft Fabric Blog | Microsof...

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.