# Inefficient use of interactive clusters | Cloud Efficiency Hub Canonical: 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... By: Matt Weingarten Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Inefficient Use of Interactive Clusters The short version Interactive clusters are intended for development and ad-hoc analysis, remaining active until manually terminated or until their auto-termination inactivity timeout elapses. 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-0008 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. When used to run scheduled jobs or production workflows, they often stay idle between executions - leading to unnecessary infrastructure and DBU costs. Job clusters are designed for ephemeral, single-job execution and automatically terminate upon completion, reducing runtime and isolating workloads. Using interactive clusters for production jobs leads to cost inefficiencies and weaker workload boundaries. ## Billing model The pricing dimensions that drive this cost. Databricks compute costs consist of: - Databricks Units (DBUs): billed per second at a rate that depends on the compute type and instance; all-purpose (interactive) compute is billed at a higher DBU rate than jobs compute, so scheduled jobs on interactive clusters pay a premium on every DBU in addition to any idle time - Cloud Infrastructure Charges: Passed through from the underlying cloud provider, billed per second or minute Interactive clusters accrue charges continuously while running, regardless of workload activity. Job clusters are provisioned on demand and shut down automatically, incurring charges only for the job's runtime. ## How to detect 5 checks to find it in your estate. - Identify scheduled jobs assigned to interactive clusters - Query system tables or logs to verify cluster assignment per job - Review cluster uptime relative to job duration to assess idle overhead - Evaluate whether workspace policies restrict interactive cluster use for jobs - Confirm with engineering teams if job clusters can be safely adopted ## How to fix 3 ways to remove the waste. - Reassign scheduled jobs to ephemeral job clusters - Apply workspace policies to enforce job cluster usage for scheduled workflows - Educate users on the differences between cluster modes and their appropriate use cases ## Documentation Vendor references for pricing and configuration. - [Compute docs.databricks.com](https://docs.databricks.com/aws/en/compute) - [Configure classic compute for Lakeflow Jobs docs.databricks.com](https://docs.databricks.com/aws/en/jobs/run-classic-jobs) ## 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-0067 ### [Inefficient Autotermination Configuration for Interactive Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-autotermination-configuration-for-interactive-clusters) Interactive clusters are often left running between periods of active use. To mitigate idle charges, Databricks provides an "autotermination" setting that shuts down clusters after a period of inactivity. However, if the termination period... 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.