Showing posts with label throttling. Show all posts
Showing posts with label throttling. Show all posts

17 November 2026

🏭🗒️Microsoft Fabric: Capacity Management [Notes]

Disclaimer: This is work in progress intended to consolidate information from various sources for learning purposes. For the latest information please consult the documentation (see the links below)! 

Last updated: 16-Nov-2026

[Microsoft Fabric] Capacity Management

  • {def} process for the administration and governance of the compute resources (CUs) available in a Fabric capacity
  • {concept} capacity 
    • {def} a dedicated set of compute resources that are available at a given time to be used
      • each capacity has fixed compute resources measured in CUs [6]
      • defines the ability of a resource to perform an activity or to produce output
      • resides in a specific region of the buyers’ choice where both the data & compute reside [3]
      • provides the compute and storage for all the workspace artifacts [3]
        • workspaces are assigned to a capacity 
    • shared across:
      • workloads
        • a single capacity provides the computing power for all Fabric workloads, and there is no need to allocate compute separately per engine.
      • projects
        • a capacity typically supports dozens of separate projects, each in its own workspace(s).
      • users
        • every user action that consumes compute (e.g. queries, refreshes, pipeline runs, notebook execution) uses the same capacity pool.
    • priced at a fixed hourly rate 
      • multiple capacities can be purchased, deployed and managed by different owners residing in a single tenant 
        • {benefit} allows each business unit to pay for their own consumption [3]
      • based on CUs provisioned [3]
      • dimensioned as a function of cores: 
        • F2=2^1, F4=2^2, ..., F32=2^5, F64=2^6, ..., F2048=2^11 (powers of 2 from 1..11)
        • ⇐ flexible building blocks for growth
        • with increased Fx it provides
          • better concurrency 
          • lower throttling risk
          • more realistic PoCs
          • better workload isolation
          • increased reliability 
      • purchased either as 
        • PAYG model
        • RI resource
        • F0 
  • {concept} Stock Keeping Unit (SKU)
    • {def} the capacity tier that determines how much compute power, memory, and overall performance a Fabric environment receives
  • {concept} capacity unit (CU) 
    • {def} the standardized measure of computing resources available to a Fabric capacity
      • used to abstract away the actual CPU cores, memory, and infrastructure so that customers can size Fabric workloads consistently
        •  measure the compute power available for each SKU [2]
    • CUs consumption is not a hard limit per SKU
      • based on an average over a 24-hour period
        • gives customers the ability to take advantage of bursting and smoothing
  • {concept} timepoint 
    • {def} internal measurement intervals MF uses to evaluate how much CU consumption is occurring over time and whether the capacity is being throttled
      •  24 hours contain 2,880 timepoints
      •  Fabric automatically manages the amount of consumed CUs in each timepoint [2]
      •  the boundaries are aligned to the Fabric service clock
      •  a workload is charged to whichever 30-second timepoint(s) are active when the work executes
  • {concept} overage
    • the amount of capacity debt that would otherwise cause throttling because a capacity has consumed more compute than its provisioned CUs can support after smoothing
      •  when overages exceed the allowed 10-minute throttling window, they become carryforward CUs [2]
        • carryforward CUs apply to each subsequent timepoint [2]
        • if a timepoint isn't full, the unused CUs reduce the carryforward CUs amount (aka burndown)
  • {operation} provisioning (aka capacity provisioning)
    • provisioned with a certain amount of compute units, analogous to CPU cores
    • there is no authoritative guide to help customers calculate the CUs required by a solution
    • {recommendation} experiment to figure out the best fit
      • allows to find the optimum size for workloads  
  • {operation} configuration (aka capacity configuration) 
    • capacities can be configured in endless ways to meet scale, usage and governance requirements while tuning to minimize TCO and performance goals [3]
  • {mechanism} bursting
    • the ability for a Fabric capacity to temporarily consume more compute resources beyond what the customer purchased, respectively beyond what was allocated for a given job
    • {benefit} job acceleration 
      • allows to speed workloads execution
        • e.g. instead of running a job on 64 CUs in 60 seconds, bursting could use 256 CUs to complete in 15 seconds
    • {benefit} use extra resources
      • allows workloads to use additional compute resources to handle spikes in capacity requirements over short periods of time
        • allows jobs to utilize far more resources than 'face value'
      • improves users’ experience
      • provides a temporary relief, until the burst allowance is eventually exhausted
      • {warning} can hide capacity sizing problems
        • because bursting absorbs occasional overloads
        • potential for future throttling, if not addressed timely
    • {characteristic} automatic 
      • automatically allocates resources as needed to execute at maximum performance [3]
        • regardless of SKU
        • {warning} one query could consume all the quota of a single time window and much more! [3]
      • when the system reasons it can accelerate the job by applying extra resources [3]
        • occurs behind the scenes, acting as a buffer
        • no settings are required [3]
  • {mechanism} smoothing (aka averaging)
    • a mechanism that spreads the CU consumption of operations across future time periods [5]
      • instead of scheduling all consumption immediately [5]
      • run when small usage bursts occur, flattening compute usage over time to help customers avoid being penalized with additional cost [5]
        • operation's utilization type determines the number of timepoints that Fabric uses for smoothing [2]
          • interactive operations are smoothed over a minimum of five minutes, and up to 64 minutes depending on how much CU usage they consume [2]
          • background operations are smoothed over a 24-hour period because [2]
            • they typically have long runtimes and large CU consumption [2]
      • ensures users can enjoy consistently fast performance without throttling [2]
        • only a portion of the CU usage for an operation applies to any individual timepoint, which reduces throttling overall [2]
        •  smoothed CU usage accumulates as operations run [2]
        • future capacity (CUs available in future timepoints) pays for smoothed usage [2]
          • because the capacity runs continuously [2]
    • bursting and smoothing work together
      • let capacities self-manage and self-heal when temporary spikes in usage would otherwise cause other systems to fail or slow down [2]
      • aren't supported when Autoscale Billing for Spark is enabled [2]
        • Spark usage operates in a PAYG mode [2]
    • {benefit} workload stabilization
      • helps capacities self-stabilize by flattening loads with large spikes into a smooth load profile, eliminating temporal spikes [3]
      • pays back that additional compute consumption when the capacity is less in demand 
        • prevents overloads as the smoothing mechanism will always flatten the resource burst [3]  
    • {benefit} scheduling contention elimination
      • large/scheduled jobs are smoothed over 24 hours [5]
        • eliminates the need to decide the timing and order of job execution [5]
        • operations are always executed for maximum performance [5]
    • {benefit} bad actor protection
      • prevents a single actor (user) with a very demanding query from hogging the entire capacity [5]
        • interactive operations are smoothed over several minutes [5]
  • {mechanism} throttling 
    • {def} protection mechanism that activates when a capacity resource consumption exceeds the capacity threshold for the current time window [5]
      • there can be a short delay before throttling begins [6]
      • running too many operations can overload a capacity [2]
        • the capacity automatically throttles new operations when it's overloaded [2]
      • happens in progressive steps [2]
        • helps to minimize the impact on important tasks like data refreshes [2]
      • not applied automatically when a capacity is operating above 100% utilization [2]
        •  see overage protection
      • an indicator that the capacity is experiencing sustained pressure [5]
        • while one capacity, or set of workspaces, might experience reduced performance from being overloaded, other capacities might continue running normally [2]
      • too much throttling can result in a degraded end-user experience [2]
      • applied at the capacity level [2]
    • starts when a capacity uses up all its CU resources for the next 10 minutes, when overage protection ends [2]
      •  
      • {phase} applies 20-second delays to new interactive operations [2]
      • {phase} rejects new interactive operations when a capacity uses up all its CU resources for the next one hour [2]
        • background operations can start and run [2]
      • {phase} rejects all new requests, interactive and background, when the capacity uses up all its available CU resources for the next 24 hours [2]
        •  the capacity continues to throttle requests until you pay off the consumed CUs [2]
      •  its enforcement continues until unused capacity pays off all carryforward CUs [2]
    • consistently high throttling levels indicate the need to either
      • load balance across multiple capacities [2]
      • increase the capacity SKU size [2]
    • {concept} throttling policies
      • {def} rules Fabric uses to slow down or reject workload execution when a capacity is overloaded
      • prevent a capacity from becoming unusable when its smoothed consumption exceeds the available Capacity Units (CUs).
      • refined to deliver multiple benefits [3]
    • reduced throttling for capacities that only experience occasional spikes [3]
    • [monitoring] Fabric capacity metrics app cane be used to confirm throttling
      • via Compute page >> System events table 
        • shows the history of t4hrottling events [2]
      • via Compute page >> Throttling charts 
        • show when smoothed usage exceeds one of the throttling limits [2]
  • {feature} capacity overage (aka overage protection)
    • {def} feature that allows a capacity to continue running when it would otherwise be throttled because the purchased CU where exceeded
  • {feature} surge protection
    • {def} mechanism that helps prevent a Fabric capacity from becoming overloaded by proactively limiting background workloads before the capacity reaches severe throttling
      • interactive operations smoothed over several minutes, preventing a single user with a very demanding query from hogging the entire capacity [3]
  • {capacity size} F0
    • a zero-provisioned capacity SKU 
      • announced at FabCon Europe Sep, 2026
    • {characteristic} billed on demand
      • no upfront compute charge
      • accommodates one billing category workloads
        • e.g. Data Warehouse
      • designed to work with on-demand billing 
        • rather than requiring customers to reserve compute capacity upfront
    • {characteristic} built-in monitoring
      • via Capacity Metrics >> 'On-demand compute' tab⠀
    • {characteristic} supports no smoothing
      • priced as a multiplier of PAYG
        • prices yet to be disclosed 
    • {advantage} start small, scale on demand
    • {disadvantage} steep learning curve
      • especially when no trial capacity is available
    • {scenario} development & testing with minimal workloads
    • {scenario} small proof-of-concepts
    • {scenario} sporadic workloads
    • {scenario} organizations wanting consumption-based billing
  • {capacity size} F2
    • entry-level capacity with access to standard Fabric features
    • best suited for lightweight, low‑volume, or exploratory workloads that don't require parallelism 
      •  useful to prove that solutions work
      • {scenario} proof-of-concepts
      • {scenario} individual usage
      • {scenario} training & testing with minimal workloads
    • can occasionally execute workloads larger than its nominal size
      •  e.g. small notebooks, warehouse queries may complete successfully 
    • {limitation} many workloads require at least F4 
      • e.g. Spark notebooks, Dataflows, Power BI refreshes), while bursting and smoothing provides less benefit; 
    • {limitation} not viable for production environments
      • very limited compute power
      • throttling occurs often 
      • poor fit for concurrent access 
      • limited refresh & ETL throughput 
  • {capacity size} F4
    • first usable production‑grade capacity for light to moderate workloads
      • ideal for PoCs, small production workloads, notebooks, though workloads may run soon into its limitations
    • allows to run concurrent activities
      • e.g. combined BI & Data Engineering 
    • includes all standard F-SKU features (Copilot, Managed Private Endpoints, etc.)
    • can support 
      • Power BI reports
      • small lakehouses
      • Data Factory pipeliness 
  • {capacity size} F8
    • generally considered strong enough for multiple developers, analysts, and BI users working at the same time
    • often support dozens to hundreds of actively used reports 
    • provides a more realistic environment for testing
      • scheduled refreshes 
      • concurrent users
      • automated pipelines
      • engineering workloads
  • {capacity size} F16
    • works well if workloads are light
    • often support dozens to hundreds of actively used reports
    • good for
      • smaller lakehouses
      • scheduled pipelines
      • moderate notebook execultion 
  • {capacity size} F32
    • suitable for mid-sized workloads, though it may be still insufficient for heavy workloads
    • often support hundreds to thousands of actively used reports.
    • good for
      • departmental BI
      • smaller semantic model
      • limited refresh schedules
    • best for
      • departmental Fabric deployments
      • medium-sized organizations
      • initial production rollouts
      • single-team ownership
  • {capacity size} F64
    • first high‑performance, enterprise‑grade Fabric capacities
      • it's designed for advanced workloads, multiple teams, and high‑throughput data operations
    • with it the licensing model for Power BI changes
      •  equivalent to a Power BI Premium-sized capacity
        •  ⇒ free Power BI user consumption 
          •  ⇐ a license is still needed for development
    • often support hundreds to thousands of actively used reports
    • often where organizations begin running
      • larger Spark workloads
      • multiple engineering team
      • more complex medallion architectures
      • heavy ingestion schedule
    • often the capacity where organizations start implementing
      • workspace isolation strategies
      • capacity governance
      • chargeback/showback
      • surge protection policies
      • dedicated engineering and BI workloads
  • {capacity size} F128+ 
    • ideal for scenarios in which multiple business units share a capacity
    • provides more flexibility in workload scheduling
    • can support very large enterprise estates with thousands of reports
    • governance becomes more important than performance 
  • {type} trial capacity
    • automatically created when a user begins to work with Fabric items in the Fabric portal
    • users are prompted to start the trial capacity [4] 
    • users using a non-Fabric-enabled workspace and who are trying to create Fabric-specific item for the first time, are automatically upgraded to a trial license for MF [4]
    • has a limitation of five trial capacities per tenant [4]
    • users can opt out between a F4 and F64 capacity
    • doesn't have access to all features
      • e.g. Copilot requires at least a F2 capacity
    • valid for 60 days from activation
      •  
  • {feature} Microsoft Fabric Capacity Metrics app 
    • allows monitoring the CUs usage to better understand how many CUs are required for operating your solution and whether you might want to consider scaling up or scaling out your Fabric SKU(s)

Previous Post <<||>> Next Post 

References:
[1] Microsoft Learn (2025) Manage your capacities in the Admin portal [link]
[2] Microsoft Learn (2026) Understand the Fabric capacity throttling policy [link]
[3] Benni De Jagere (202x) Understanding Fabric Capacities
[4] Brian Bønk & Valerie Junk (2026) Microsoft Fabric Analytics Engineer Associate Study Guide: Hands-On Practice and Expert Tips for Acing the DP600 Certification Exam
[5] Microsoft Learn (2026) Microsoft Fabric: Advanced Real-Time Intelligence
[6] Capacity overage in Microsoft Fabric [link]

Acronyms:
BI - Business Intellgience
CI/CD - Continuous Integration and Continuous Deployment
CU - Capacity Unit
IDE - Integrated Development Environments
MF - Microsoft Fabric 
PAYG - Pay-As-You-Go
SKU - Stock Keeping Unit 

Related Posts Plugin for WordPress, Blogger...

About Me

My photo
Koeln, NRW, Germany
IT Professional with more than 25 years experience in IT in the area of full life-cycle of Web/Desktop/Database Applications Development, Software Engineering, Consultancy, Data Management, Data Quality, Data Migrations, Reporting, ERP implementations & support, Team/Project/IT Management, etc.