So databricks actually suggests starting with a larger than needed size and then sizing down as needed. Could we link to this or add some blurb about it?

https://urldefense.com/v3/__https://docs.google.com/forms/d/e/1FAIpQLSfkdUlvsWpA6pRb7rWZ1_dMZ8jfZYqfyG5bkvBB5pxRZQMAsg/viewform__;!!NCc8flgU!dYlizNl-ZzMuUyE6TGPHnapA-R93lsttvpzwR90VX6vCsT3s0uXc9P7tziUMiid8bCVuakL0SYGqOV_3w8CcSjPF4oE$

Always start with a larger t-shirt size for your serverless SQL warehouse than you think you will need and size down as you test. Don’t start with a small t-shirt size for your serverless SQL warehouse and go up. In general, start with a single serverless SQL warehouse and rely on Databricks to right-size with serverless clusters, prioritizing workloads, and fast data reads. See Serverless autoscaling and query queuing.

@SyedWasiHaider I've linked to the Databricks article you provided. Once Sriram's back, I can also circle back to see if he wants to update any additional sizing verbiage in this section