Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi,
we are currently observing that the same SQL queries (against the same data) show strong fluctuations in CU consumption.
Same behavior with the Lakehouse SQL Endpoint.
These spikes occur about every 3rd query.
Nothing else was executed while the query was running.
Do I have any way to see why ? Or is it just “bad luck” with the query plan or something?
HI @JDT,
According to your description, I think they may related to the capacity policy and throttling smooth.
Fabric is designed to deliver lightning-fast performance to its customers by allowing operations to access more capacity unit (CU) resources than are allocated to the capacity. Tasks that might take several minutes to complete on other platforms can be finished in mere seconds on Fabric. To avoid penalizing users when operational loads surge, Fabric smooths or averages the CU usage of an operation over a minimum of five minutes, and even longer for high CU usage but short runtime requests. This behavior ensures you can enjoy consistently fast performance without experiencing throttling.
You can take a look at the following document to know more about these:
Understand your Fabric capacity throttling - Microsoft Fabric | Microsoft Learn
Regards,
Xiaoxin Sheng
Our capacity was utilized to around 35% and the queries consumed between 0.15% and 0.45% of the base capacity.
I dont think throttling is the issue here.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
3 | |
1 | |
1 | |
1 | |
1 |
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |