- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2021
08:27 PM
- last edited
a week ago
by
Advika
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2021 11:12 AM
When sizing, this is the recommendation.
Data set Cluster Size
ITB / rows X-Large+
500GB / 1B rows X-Large
SOGB / IOOM+ rows Large
IOOGB / rows Medium
IOGB / -M rows Small
This table maps SQL endpoint cluster sizes to Databricks cluster driver sizes and worker counts. All workers are i3.2xlarge.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2021 11:10 AM
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 auto-scale (add a new cluster) when processing approximately 10 parallel requests.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2021 11:12 AM
When sizing, this is the recommendation.
Data set Cluster Size
ITB / rows X-Large+
500GB / 1B rows X-Large
SOGB / IOOM+ rows Large
IOOGB / rows Medium
IOGB / -M rows Small
This table maps SQL endpoint cluster sizes to Databricks cluster driver sizes and worker counts. All workers are i3.2xlarge.

