Test stress for fabric capacity

Hello AstridM,

You have a Microsoft Fabric F64 capacity and are receiving emails indicating the capacity reached 75%. 

You don't have to do a stress test to understand throttling in the capacity, here is the link for the consequence when your capacity exceed his limit : https://learn.microsoft.com/en-us/fabric/enterprise/throttling

Throttling in Fabric does not generate extra cost. It is not like cloud auto-scaling where you “pay more.” Instead, workloads are slowed down or queued (background and interactive task) to remain within the purchased capacity.

• Typical effects of throttling include:

  • Queries taking longer to start or execute.

  • Refreshes/pipelines queued until resources are available.

  • Spark notebooks waiting longer to acquire a kernel.

  • In rare cases, timeouts if the queue delay exceeds limits.

You can first Understand Current Usage : 

• Use the Fabric Capacity Metrics App to analyze historical CU consumption.

• Identify the heaviest workloads (e.g., Power BI refreshes, SQL queries, Spark notebooks).

• Look at who/what consumes the most CUs and at what times.

Hope it can help you ! 

Best regards,

Antoine