<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Large deviation in CU consumption - same sql query in Data Warehouse</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Warehouse/Large-deviation-in-CU-consumption-same-sql-query/m-p/4142833#M1616</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;we are currently observing that the same SQL queries (against the same data) show strong fluctuations in CU consumption.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Same behavior with the Lakehouse SQL Endpoint.&lt;BR /&gt;These spikes occur about every 3rd query.&lt;/P&gt;&lt;P&gt;Nothing else was executed while the query was running.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do I have any way to see why ? Or is it just “bad luck” with the query plan or something?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 10 Sep 2024 13:01:51 GMT</pubDate>
    <dc:creator>JDT</dc:creator>
    <dc:date>2024-09-10T13:01:51Z</dc:date>
    <item>
      <title>Large deviation in CU consumption - same sql query</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Warehouse/Large-deviation-in-CU-consumption-same-sql-query/m-p/4142833#M1616</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;we are currently observing that the same SQL queries (against the same data) show strong fluctuations in CU consumption.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Same behavior with the Lakehouse SQL Endpoint.&lt;BR /&gt;These spikes occur about every 3rd query.&lt;/P&gt;&lt;P&gt;Nothing else was executed while the query was running.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do I have any way to see why ? Or is it just “bad luck” with the query plan or something?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2024 13:01:51 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Warehouse/Large-deviation-in-CU-consumption-same-sql-query/m-p/4142833#M1616</guid>
      <dc:creator>JDT</dc:creator>
      <dc:date>2024-09-10T13:01:51Z</dc:date>
    </item>
    <item>
      <title>Re: Large deviation in CU consumption - same sql query</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Warehouse/Large-deviation-in-CU-consumption-same-sql-query/m-p/4143822#M1620</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="798920" data-lia-user-login="JDT" class="lia-mention lia-mention-user"&gt;JDT&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;According to your description, I think they may related to the capacity policy and throttling smooth.&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#808080"&gt;&lt;EM&gt;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.&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;You can take a look at the following document to know more about these:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/fabric/enterprise/throttling#throttle-triggers-and-throttle-stages" target="_blank"&gt;Understand your Fabric capacity throttling - Microsoft Fabric | Microsoft Learn&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Xiaoxin Sheng&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2024 01:41:55 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Warehouse/Large-deviation-in-CU-consumption-same-sql-query/m-p/4143822#M1620</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-09-11T01:41:55Z</dc:date>
    </item>
    <item>
      <title>Re: Large deviation in CU consumption - same sql query</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Warehouse/Large-deviation-in-CU-consumption-same-sql-query/m-p/4144838#M1624</link>
      <description>&lt;P&gt;Our capacity was utilized to around 35% and the queries consumed between 0.15% and 0.45% of the base capacity.&lt;/P&gt;&lt;P&gt;I dont think throttling is the issue here.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2024 11:53:01 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Warehouse/Large-deviation-in-CU-consumption-same-sql-query/m-p/4144838#M1624</guid>
      <dc:creator>JDT</dc:creator>
      <dc:date>2024-09-11T11:53:01Z</dc:date>
    </item>
  </channel>
</rss>

