# Inefficient use of Photon engine in Databricks compute Canonical: 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. By: Josh Collier Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Inefficient Use of Photon Engine in Databricks Compute The short version Photon is enabled by default on many Databricks compute configurations. [Josh Collier](https://www.linkedin.com/in/josh-collier-945b7029/) FinOps Lead @ Superhuman 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-0159 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. While it can accelerate certain SQL and DataFrame operations, its performance benefits are workload-specific and may not justify the increased DBU cost. Many pipelines, particularly ETL jobs or simpler Spark workloads, do not benefit materially from Photon but still incur the higher DBU multiplier. Disabling Photon by default and allowing it only where proven beneficial can reduce cost without degrading performance. ## Billing model The pricing dimensions that drive this cost. Databricks charges based on Databricks Units (DBUs), which are consumed per node per hour. Photon compute consumes DBUs at a higher rate than the same instance type without Photon; the multiplier depends on the cloud, instance type, and compute type, so check the Databricks pricing calculator for current rates. While Photon can significantly reduce runtime for certain workloads, in many environments the performance benefit is marginal, resulting in higher cost without proportional gain. ## How to detect 4 checks to find it in your estate. - Identify compute clusters or jobs with Photon enabled - Review job configurations for SKUs or node types with Photon in the name - Check cluster configuration settings for the Photon toggle - Evaluate job-level performance data to determine if Photon meaningfully reduces runtime for the associated workload ## How to fix 3 ways to remove the waste. - Update default compute configurations to disable Photon for general-purpose or low-complexity workloads - Restrict users from enabling Photon unless justified by benchmarked performance gains - Establish cluster policies or templates that exclude Photon by default and allow opt-in only under specific conditions ## Documentation Vendor references for pricing and configuration. [Photon Runtime on Databricks](https://docs.databricks.com/aws/en/compute/photon) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - 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-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.