# Oversized worker or driver nodes in Databricks clusters Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/oversized-worker-or-driver-nodes-in-databricks-clusters Databricks users can select from a wide range of instance types for cluster driver and worker nodes. By: Matt Weingarten Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Oversized Worker or Driver Nodes in Databricks Clusters The short version Databricks users can select from a wide range of instance types for cluster driver and worker nodes. 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-0125 Type Overprovisioned Resource ## Explanation Why the waste happens and who it affects. Without guardrails, teams may choose high-cost configurations (e.g., 16xlarge nodes) that exceed workload requirements. This results in inflated costs with little performance benefit. To reduce this risk, administrators can use compute policies to define acceptable node types and enforce size limits across the workspace. ## Billing model The pricing dimensions that drive this cost. Databricks costs are driven by: - Databricks Units (DBUs): Rated per hour based on node type, with usage billed at per-second granularity - Cloud Infrastructure Charges: Cost of underlying VMs, billed per second or minute Larger node types (e.g., high-memory or high-I/O VMs) incur significantly higher charges. Oversizing clusters without justification leads to unnecessary DBU and infrastructure costs. ## How to detect 4 checks to find it in your estate. - Review all cluster configurations to identify usage of large or high-cost instance types - Query system tables for driver and worker node types across clusters - Check whether compute policies are in place to limit allowable node sizes - Engage with workload owners to confirm whether large instances are justified based on workload characteristics ## How to fix 3 ways to remove the waste. - Define and enforce compute policies that restrict driver and worker node types to appropriate sizes - Reconfigure existing clusters using oversized nodes to use smaller, cost-effective alternatives - Allow exceptions only for workloads that demonstrably require high-performance nodes ## Documentation Vendor references for pricing and configuration. - [Cluster Sizing Guidelines docs.databricks.com](https://docs.databricks.com/aws/en/compute/cluster-config-best-practices) - [Compute Policies in Databricks docs.databricks.com](https://docs.databricks.com/aws/en/admin/clusters/policies) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - 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 - 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-0022 ### [Missing Auto-Termination Policy for Databricks Clusters](https://www.pointfive.co/efficiency-hub/inefficiencies/missing-auto-termination-policy-for-databricks-clusters) In many environments, users launch Databricks clusters for development or analysis and forget to shut them down after use. When no auto-termination policy is configured, these clusters remain active indefinitely, incurring unnecessary... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.