<?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 How to implement automatic scaling of cluster size in Serverless Warehouse in Warehousing &amp; Analytics</title>
    <link>https://community.databricks.com/t5/warehousing-analytics/how-to-implement-automatic-scaling-of-cluster-size-in-serverless/m-p/110240#M1881</link>
    <description>&lt;P&gt;&lt;SPAN&gt;I would like to know if the &lt;/SPAN&gt;cluster size&lt;SPAN&gt; of a Serverless Warehouse can automatically scale up and down, and what determines the number of workers used when executing queries. Does it use all workers within the cluster size fixedly, or does it use part or all of the workers in a cluster according to the query plan?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 14 Feb 2025 14:36:23 GMT</pubDate>
    <dc:creator>fishingrod</dc:creator>
    <dc:date>2025-02-14T14:36:23Z</dc:date>
    <item>
      <title>How to implement automatic scaling of cluster size in Serverless Warehouse</title>
      <link>https://community.databricks.com/t5/warehousing-analytics/how-to-implement-automatic-scaling-of-cluster-size-in-serverless/m-p/110240#M1881</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I would like to know if the &lt;/SPAN&gt;cluster size&lt;SPAN&gt; of a Serverless Warehouse can automatically scale up and down, and what determines the number of workers used when executing queries. Does it use all workers within the cluster size fixedly, or does it use part or all of the workers in a cluster according to the query plan?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2025 14:36:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/warehousing-analytics/how-to-implement-automatic-scaling-of-cluster-size-in-serverless/m-p/110240#M1881</guid>
      <dc:creator>fishingrod</dc:creator>
      <dc:date>2025-02-14T14:36:23Z</dc:date>
    </item>
    <item>
      <title>Re: How to implement automatic scaling of cluster size in Serverless Warehouse</title>
      <link>https://community.databricks.com/t5/warehousing-analytics/how-to-implement-automatic-scaling-of-cluster-size-in-serverless/m-p/110241#M1882</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/149262"&gt;@fishingrod&lt;/a&gt;,&lt;/P&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;Yes, the cluster size of a Serverless Warehouse can automatically scale up and down. The autoscaling behavior is managed by Intelligent Workload Management (IWM), which dynamically adjusts the compute resources based on the workload demands. This system uses machine learning models to predict the resource needs of incoming queries and monitors the warehouse’s available compute capacity in real time.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;The number of workers used when executing queries is not fixed. Instead, the system scales the number of resources to accommodate varying demands. The autoscaling mechanism ensures that compute resources are rapidly upscaled to maintain low latency and quickly downscaled to minimize costs when demand is low. This dynamic management allows the warehouse to handle large numbers of queries efficiently and cost-effectively.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="_1t7bu9h1 paragraph"&gt;&lt;SPAN&gt;Please see:&amp;nbsp;&lt;A href="https://docs.databricks.com/en/compute/sql-warehouse/warehouse-behavior.html" target="_blank"&gt;https://docs.databricks.com/en/compute/sql-warehouse/warehouse-behavior.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2025 14:59:08 GMT</pubDate>
      <guid>https://community.databricks.com/t5/warehousing-analytics/how-to-implement-automatic-scaling-of-cluster-size-in-serverless/m-p/110241#M1882</guid>
      <dc:creator>Alberto_Umana</dc:creator>
      <dc:date>2025-02-14T14:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: How to implement automatic scaling of cluster size in Serverless Warehouse</title>
      <link>https://community.databricks.com/t5/warehousing-analytics/how-to-implement-automatic-scaling-of-cluster-size-in-serverless/m-p/110294#M1884</link>
      <description>&lt;P&gt;So what is the purpose of the `cluster size` I set when I created the Serverless Warehouse? Isn’t it automatically adjusted?&lt;/P&gt;</description>
      <pubDate>Sat, 15 Feb 2025 09:07:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/warehousing-analytics/how-to-implement-automatic-scaling-of-cluster-size-in-serverless/m-p/110294#M1884</guid>
      <dc:creator>fishingrod</dc:creator>
      <dc:date>2025-02-15T09:07:52Z</dc:date>
    </item>
    <item>
      <title>Re: How to implement automatic scaling of cluster size in Serverless Warehouse</title>
      <link>https://community.databricks.com/t5/warehousing-analytics/how-to-implement-automatic-scaling-of-cluster-size-in-serverless/m-p/110298#M1885</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/149262"&gt;@fishingrod&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My understanding is that Intelligent Workload Management (IWM) in Serverless SQL Warehouses adjusts the &lt;STRONG&gt;number&lt;/STRONG&gt; of clusters, but it does not automatically scale the cluster &lt;STRONG&gt;size&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;This means that if you need to improve the execution performance of individual SQL queries, you will need to explicitly specify the cluster size yourself.&lt;/P&gt;</description>
      <pubDate>Sat, 15 Feb 2025 14:04:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/warehousing-analytics/how-to-implement-automatic-scaling-of-cluster-size-in-serverless/m-p/110298#M1885</guid>
      <dc:creator>Takuya-Omi</dc:creator>
      <dc:date>2025-02-15T14:04:01Z</dc:date>
    </item>
  </channel>
</rss>

