# Idle Snowpark Container Services Compute Pools Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/idle-snowpark-container-services-compute-pools Snowpark Container Services (SPCS) runs containerized services and jobs on compute pools, which are collections of virtual machine nodes of a chosen... By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version Snowpark Container Services (SPCS) runs containerized services and jobs on compute pools, which are collections of virtual machine nodes of a chosen instance family. PointFive Research Cloud cost research at PointFive Snowflake service [Snowpark Container Services](https://www.pointfive.co/efficiency-hub/cloud-services/snowpark-container-services) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0520 Type Idle or Unused Resource ## Explanation Why the waste happens and who it affects. A pool is billed for its nodes whenever it is in the IDLE, ACTIVE, STOPPING or RESIZING state, and only stops billing when it is SUSPENDED. A pool can only auto-suspend when no services and no jobs are running on any of its nodes, so a single long-running service that nobody calls keeps the whole pool, and at least MIN\_NODES nodes, billing around the clock. Typical cases are pools created for experiments, demos, notebooks and internal apps that are used a few hours a week. Services do not auto-suspend by default (a service's AUTO\_SUSPEND\_SECS defaults to 0), so a forgotten service pins its pool active. Pools are also created with AUTO\_SUSPEND\_SECS set to 0, which disables automatic suspension, or with MIN\_NODES higher than the steady workload needs, and GPU pools make any idle time especially expensive. Snowflake's SPCS cost guidance recommends using AUTO\_SUSPEND to manage these charges. ## Billing model The pricing dimensions that drive this cost. Compute pool node credits Each node consumes Platform Credits per hour at the rate for its instance family, charged per second while the pool is IDLE, ACTIVE, STOPPING or RESIZING Node start minimum The Service Consumption Table applies a minimum of five minutes of credits each time a compute node is started or resumed Suspended pool No compute charges while the pool is STARTING or SUSPENDED; storage for images, volumes and logs is billed separately Data transfer Outbound and internal transfer for SPCS is billed at rates in the Service Consumption Table, except for accounts on Google Cloud where it is currently not billed ## How to detect 5 checks to find it in your estate. - Run SHOW COMPUTE POOLS and review state, num\_services, num\_jobs, active\_nodes, idle\_nodes, min\_nodes and auto\_suspend\_secs; flag pools that are ACTIVE or IDLE with no workloads, pools with auto\_suspend\_secs = 0, and pools with idle nodes above need - Query SNOWFLAKE.ACCOUNT\_USAGE.SNOWPARK\_CONTAINER\_SERVICES\_HISTORY (hourly CREDITS\_USED per COMPUTE\_POOL\_NAME) to find pools billing continuously, including nights and weekends - Run SHOW SERVICES IN COMPUTE POOL \ for pools that never suspend and identify services with no recent callers, checking their auto\_suspend\_secs, which defaults to 0 - Check METERING\_HISTORY where SERVICE\_TYPE = 'SNOWPARK\_CONTAINER\_SERVICES' to track total SPCS spend over time and spot pools that outlived their project - Separate pools created by Native Apps (IS\_EXCLUSIVE and APPLICATION\_NAME in the history view) and review them with the app owner ## How to fix 5 ways to remove the waste. - Drop services and pools that are no longer used (DROP SERVICE, then DROP COMPUTE POOL), or use ALTER COMPUTE POOL ... STOP ALL to drop all services and cancel jobs in a pool before removing it - Set AUTO\_SUSPEND\_SECS on services with intermittent use (minimum 300 seconds, counted as no queries invoking a service function) with AUTO\_RESUME left TRUE, so idle services release the pool; expect start-up latency on the first request after a suspend - Keep a non-zero AUTO\_SUSPEND\_SECS on every compute pool (ALTER COMPUTE POOL ... SET AUTO\_SUSPEND\_SECS = \; the default for new pools is 3600) so the pool suspends once no services or jobs are running - Suspend pools during known idle periods with ALTER COMPUTE POOL ... SUSPEND, which suspends all services in the pool while jobs run to completion, and RESUME before use - Lower MIN\_NODES to what the steady workload needs and let MAX\_NODES absorb peaks, and pick the smallest instance family that fits, reserving GPU families for workloads that need them ## Documentation Vendor references for pricing and configuration. - [Snowpark Container Services costs docs.snowflake.com](https://docs.snowflake.com/en/developer-guide/snowpark-container-services/accounts-orgs-usage-views) - [CREATE COMPUTE POOL docs.snowflake.com](https://docs.snowflake.com/en/sql-reference/sql/create-compute-pool) - [ALTER COMPUTE POOL docs.snowflake.com](https://docs.snowflake.com/en/sql-reference/sql/alter-compute-pool) - [CREATE SERVICE docs.snowflake.com](https://docs.snowflake.com/en/sql-reference/sql/create-service) - [SNOWPARK\_CONTAINER\_SERVICES\_HISTORY view docs.snowflake.com](https://docs.snowflake.com/en/sql-reference/account-usage/snowpark_container_services_history) - [Snowflake Service Consumption Table snowflake.com](https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - 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 - Snowflake Query Processing CER-0112 ### [Inefficient Execution of Repeated Queries](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-execution-of-repeated-queries) Inefficient execution of repeated queries occurs when common query patterns are frequently executed without optimization. Even if individual executions are successful, repeated inefficiencies compound overall compute consumption and credit... Compute - Snowflake Virtual Warehouse CER-0132 ### [Suboptimal Warehouse Auto-Suspend Configuration](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. Tightening the auto-suspend window ensures that the warehouse shuts down quickly once queries complete, minimizing credit waste while... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.