# Inefficient autotermination configuration for interactive clusters Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-autotermination-configuration-for-interactive-clusters Interactive clusters are often left running between periods of active use. By: Matt Weingarten Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Inefficient Autotermination Configuration for Interactive Clusters The short version Interactive clusters are often left running between periods of active use. Matt Weingarten Databricks service [Databricks Clusters](https://www.pointfive.co/efficiency-hub/cloud-services/databricks-clusters) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0067 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. To mitigate idle charges, Databricks provides an "autotermination" setting that shuts down clusters after a period of inactivity. However, if the termination period is set too high, or if policies do not enforce reasonable thresholds, idle clusters can persist for long durations without performing any work - resulting in wasted compute spend. Lowering the termination window reduces exposure to idle time while preserving user flexibility. ## Billing model The pricing dimensions that drive this cost. Databricks compute is billed via: - Databricks Units (DBUs): Rated per hour based on compute type and node configuration, and billed per second - Underlying Cloud Infrastructure: Charged based on VM runtime, billed per second or minute Interactive clusters continue accruing DBU and VM costs while running, including during idle periods. The autotermination setting determines how long idle clusters persist before being shut down automatically. Longer termination windows result in more idle time and unnecessary cost. ## How to detect 3 checks to find it in your estate. - List all interactive clusters and review their configured autotermination settings - Compare termination time thresholds to workspace policy guidelines or best practices - Confirm whether any long windows are tied to justified use cases (e.g., infrequent but heavy dev work) ## How to fix 3 ways to remove the waste. - Lower the autotermination threshold for interactive clusters - Apply workspace compute policies to cap the maximum idle time for clusters - Grant exceptions only when use cases are documented and cost impact is understood ## Documentation Vendor references for pricing and configuration. - [Manage classic compute docs.databricks.com](https://docs.databricks.com/aws/en/compute/clusters-manage) - [Create and manage compute policies docs.databricks.com](https://docs.databricks.com/aws/en/admin/clusters/policies) - [Compute policy reference docs.databricks.com](https://docs.databricks.com/aws/en/admin/clusters/policy-definition) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Databricks Clusters CER-0159 ### [Inefficient Use of Photon Engine in Databricks Compute](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-use-of-photon-engine-in-databricks-compute) Photon is enabled by default on many Databricks compute configurations. While it can accelerate certain SQL and DataFrame operations, its performance benefits are workload-specific and may not justify the increased DBU cost. Many... Compute - Databricks Clusters CER-0008 ### [Inefficient Use of Interactive Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-use-of-interactive-clusters) Interactive clusters are intended for development and ad-hoc analysis, remaining active until manually terminated or until their auto-termination inactivity timeout elapses. When used to run scheduled jobs or production workflows, they... Compute - Databricks Clusters CER-0098 ### [On-Demand-Only Configuration for Non-Production Databricks Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/on-demand-only-configuration-for-non-production-databricks-clusters) In non-production environments - such as development, testing, and experimentation-many teams default to on-demand nodes out of habit or caution. However, Databricks offers built-in support for using spot instances safely. Its job... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.