https://community.databricks.com/t5/warehousing-analytics/how-do-i-know-which-sql-endpoint-size-to-choose/m-p/24178#M609 Fri, 21 Mar 2025 12:56:22 GMT User16826992666 2025-03-21T12:56:22Z https://community.databricks.com/t5/warehousing-analytics/how-do-i-know-which-sql-endpoint-size-to-choose/m-p/24178#M609 Fri, 21 Mar 2025 12:56:22 GMT https://community.databricks.com/t5/warehousing-analytics/how-do-i-know-which-sql-endpoint-size-to-choose/m-p/24178#M609 User16826992666 2025-03-21T12:56:22Z https://community.databricks.com/t5/warehousing-analytics/how-do-i-know-which-sql-endpoint-size-to-choose/m-p/24179#M610 <P>In general, we can say that bigger clusters will process big queries faster and improve throughput. You should keep in mind that bigger clusters will not help in serving more concurrent queries. Endpoints will <B>auto-scale</B> (add a new cluster) when processing approximately <B>10 parallel requests</B>.&nbsp;</P> Tue, 22 Jun 2021 18:10:17 GMT https://community.databricks.com/t5/warehousing-analytics/how-do-i-know-which-sql-endpoint-size-to-choose/m-p/24179#M610 Digan_Parikh 2021-06-22T18:10:17Z https://community.databricks.com/t5/warehousing-analytics/how-do-i-know-which-sql-endpoint-size-to-choose/m-p/24180#M611 <P>When sizing, this is the recommendation. </P><P>Data set Cluster Size</P><P>ITB / rows X-Large+</P><P>500GB / 1B rows X-Large</P><P>SOGB / IOOM+ rows Large</P><P>IOOGB / rows Medium</P><P>IOGB / -M rows Small</P><P>This table maps SQL endpoint cluster sizes to Databricks cluster driver sizes and worker counts. All workers are i3.2xlarge.&nbsp;</P><P></P> Tue, 22 Jun 2021 18:12:41 GMT https://community.databricks.com/t5/warehousing-analytics/how-do-i-know-which-sql-endpoint-size-to-choose/m-p/24180#M611 Digan_Parikh 2021-06-22T18:12:41Z