Still called Photon in current Databricks docs (page last updated Sep 11, 2026). Documented as the Databricks-native vectorized query engine; the page describes it only inside Databricks compute (serverless, SQL warehouses, classic all-purpose and jobs compute, Lakeflow pipelines). No offering outside Databricks was found on this page.
Read
10 Nov 2026
What it does well
Per Databricks's documentation, Photon works with existing Spark API code with no changes, and it is on by default for classic all-purpose and jobs compute.
Databricks announced a TPC-audited 100 TB TPC-DS result of 32,941,245 QphDS in November 2021.
Where it is limited
Photon is documented only as part of Databricks compute and is not offered as a standalone engine for open source Spark or EMR.
Per the same documentation, Photon does not support UDFs, RDD APIs or Dataset APIs, and stateful streaming is not supported.
Published speed results
Fact
Source type
Source, read
Docs claim up to 5x better price/performance for data and analytics workloads compared to other cloud data warehouses, as measured by industry-standard TPC-DS benchmarks. This compares against warehouses, not against open source Spark.
The SIGMOD 2022 Photon paper reports customers observed average speedups of 3x over the previous Databricks Runtime and maximum speedups of over 10x. The baseline is Databricks' own prior Spark-based runtime, not open source Spark.
Databricks announced an audited 100TB TPC-DS record in November 2021: 32,941,245 QphDS versus 14,861,137 for the previous record holder (Alibaba). The post says Databricks SQL 'is not based on Apache Spark, but rather Photon'. The run was on Databricks SQL, not a Spark batch job.
Photon instance types consume DBUs at a different rate than the same instance without Photon, so cost depends on the DBU multiplier on the pricing page, not only on speedup. Databricks defines a DBU as a normalized unit of processing power used for pricing.
Docs say Photon works with existing Spark API code with no changes. Unsupported operations fall back transparently to the Spark runtime for the remainder of that operation. Photon does not support UDFs, RDD APIs or Dataset APIs, and stateful streaming is not supported.
Photon is on by default for classic all-purpose, jobs compute and classic pipelines (checkbox Use Photon Acceleration), and enabled on serverless and SQL warehouses. If you use the Clusters or Jobs API you must set runtime_engine to PHOTON. Queries under about two seconds see no meaningful gain. Users check the Spark UI to see fallback.
Photon accelerates Delta Lake, Apache Iceberg and Parquet writes, supports SQL and DataFrame APIs in Python, R, Scala and Java, and stateless streaming from Delta, Parquet, CSV, JSON, Kafka and Kinesis. It runs on Databricks Runtime, so the Spark version is the Databricks Runtime version, not a user choice of open source Spark.
Photon is documented only as part of Databricks compute on AWS, Azure and GCP (cloud tabs on the page). It is not offered as a standalone engine for open source Spark, EMR or other platforms in the docs read.
Photon supports a set of driver and worker instance types including Graviton. Graviton with Photon does not support Databricks Container Services for dedicated compute or SQL warehouses.
The TPC-DS record is a TPC-audited result, so a full report exists under TPC rules, but it needs a Databricks SQL warehouse and is not a repeatable open script. No public repo for Photon speedups on user Spark jobs was found.
Photon is the Databricks-native vectorized query engine. It replaces the JVM Spark SQL execution layer with a C++ runtime for supported operations while Catalyst still plans the query.
32,941,245 QphDS at 100 TB, against 14,861,137 QphDS for the previous record holder (Alibaba)
Databricks, audited by the TPC (its maker)
No (a TPC audit report exists under TPC rules; not a repeatable open script)
Change Budget row
Column
What changes
Detail
Source, read
Code
No change, with listed exceptions
Databricks says Photon works with existing Spark API code with no changes. It does not support UDFs, RDD APIs or Dataset APIs, and stateful streaming is not supported.
Photon is on by default for classic all-purpose, jobs compute and classic pipelines. With the Clusters or Jobs API you must set runtime_engine to PHOTON. Photon instance types use a different DBU rate.
Photon runs only inside Databricks. Photon instance types consume DBUs at a different rate than the same instance without Photon, so cost depends on the DBU multiplier on the pricing page.
Independent third-party benchmark of Photon vs open source Spark on batch ETL (searched: docs.databricks.com/en/compute/photon.html, databricks.com/blog/2021/11/02/databricks-sets-official-data-warehousing, people.eecs.berkeley.edu/~matei/papers/2022/sigmod_photon.pdf)
Databricks Photon side by side with each other option