# Suboptimal warehouse auto-suspend configuration Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-warehouse-auto-suspend-configuration If auto-suspend settings are too high, warehouses can sit idle and continue accruing unnecessary charges. By: Simar Arora Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Suboptimal Warehouse Auto-Suspend Configuration The short version If auto-suspend settings are too high, warehouses can sit idle and continue accruing unnecessary charges. [Simar Arora](https://www.linkedin.com/in/simarpreet-arora/) Value Engineer - FinOps @ Snowflake Snowflake service [Snowflake Virtual Warehouse](https://www.pointfive.co/efficiency-hub/cloud-services/snowflake-virtual-warehouse) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0132 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. Tightening the auto-suspend window ensures that the warehouse shuts down quickly once queries complete, minimizing credit waste while maintaining acceptable user experience (e.g., caching needs, interactive performance). ## Billing model The pricing dimensions that drive this cost. - Virtual warehouses consume Snowflake credits at an hourly rate set by warehouse size; each size step up roughly doubles the credits charged per hour - Credits are billed per second while a warehouse is running, with a 60-second minimum each time the warehouse starts or resumes - A suspended warehouse consumes no credits, so the auto-suspend setting determines how long an idle warehouse keeps billing after its last query finishes ## How to detect 4 checks to find it in your estate. - Review auto-suspend settings for each warehouse to identify configurations with unnecessarily high idle time thresholds (e.g., exceeding 5 minutes). - Analyze query frequency and typical idle patterns to evaluate whether warehouses could be suspended sooner without materially impacting performance. - Confirm whether workloads rely heavily on caching benefits for user facing workloads, which may justify slightly longer suspend timers. - Validate proposed changes with application teams to ensure that faster auto-suspend does not introduce unacceptable query latency. ## How to fix 5 ways to remove the waste. - Adjust warehouse auto-suspend settings to minimize idle billing while balancing performance needs. - For batch and non-interactive workloads, consider shorter suspend intervals (e.g., around 60 seconds), recognizing that minimum billing granularity is already 60 seconds. - For interactive workloads where query caching significantly improves performance, moderate suspend timers (e.g., up to 5 minutes) may be justified. - Communicate cache loss implications to workload owners to ensure informed decisions about suspend timing. - Periodically reassess suspend policies as workload patterns and user experience expectations evolve. ## Documentation Vendor references for pricing and configuration. - [Understanding compute cost docs.snowflake.com](https://docs.snowflake.com/en/user-guide/cost-understanding-compute) - [Warehouse considerations docs.snowflake.com](https://docs.snowflake.com/en/user-guide/warehouses-considerations) - [Overview of warehouses docs.snowflake.com](https://docs.snowflake.com/en/user-guide/warehouses-overview) - [ALTER WAREHOUSE docs.snowflake.com](https://docs.snowflake.com/en/sql-reference/sql/alter-warehouse) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Snowflake Virtual Warehouse CER-0129 ### [Suboptimal Query Timeout Configuration](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-query-timeout-configuration) 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.... Compute - Snowflake Virtual Warehouse CER-0514 ### [Snowflake Multi-Cluster Warehouse Pinned to Maximized Mode](https://www.pointfive.co/efficiency-hub/inefficiencies/snowflake-multi-cluster-warehouse-pinned-to-maximized-mode) 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... Compute - Snowflake Virtual Warehouse CER-0168 ### [Underutilized Snowflake Warehouse](https://www.pointfive.co/efficiency-hub/inefficiencies/underutilized-snowflake-warehouse) 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)... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.