6 documented Snowflake Virtual Warehouse cost inefficiencies, each with how to detect it and how to fix it.
Snowflake Virtual WarehouseCER-0168
Underutilized Snowflake warehouses occur when a workload is assigned a larger warehouse size than necessary. For example, a workload that could efficiently execute on a Medium (M) warehouse may be running on a Large (L) or Extra Large (XL)...
Snowflake Virtual WarehouseCER-0132
If auto-suspend settings are too high, warehouses can sit idle and continue accruing unnecessary charges. Tightening the auto-suspend window ensures that the warehouse shuts down quickly once queries complete, minimizing credit waste while...
Snowflake Virtual WarehouseCER-0129
If no appropriate query timeout is configured, inefficient or runaway queries can execute for extended periods (up to the default 2-day system limit). For as long as the query is running, the warehouse will remain active and accrue costs....
Snowflake Virtual WarehouseCER-0141
Many organizations assign separate Snowflake warehouses to individual business units or teams to simplify chargebacks and operational ownership. This often results in redundant and underutilized warehouses, as workloads frequently do not...
Snowflake Virtual WarehouseCER-0513
Snowflake consumption is open-ended by default: any role that can use a warehouse can keep it running, and serverless features and AI services consume credits without a warehouse at all. Without resource monitors or budgets, nothing...
Snowflake Virtual WarehouseCER-0514
A multi-cluster warehouse (Enterprise Edition and above) can run several clusters of the same size to absorb concurrent queries. When its minimum and maximum cluster counts are set to the same value greater than 1, it runs in Maximized...
