Side by side, read 10 Nov 2026
Databricks Photon and Flarion: the published facts in the same rows
Databricks Photon profileFlarion profile
The same rows for both
| Row | Databricks Photon | Flarion |
|---|---|---|
| Kind | Databricks's C++ vectorized engine | Rust and DataFusion engine as one JAR |
| 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. | Flarion lists prices: $0.009 per CPU hour for self-hosted Spark, $0.012 for fully managed Spark such as EMR, $0.095 per DBU on Databricks and $0.75 per CPU per month on premises. Its benchmarks page publishes the machine, Spark 3.5.5 baseline, engine builds, memory budgets and per-query caps, and discloses that q72 is counted at vanilla Spark's time for Gluten and Comet. |
| 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. | Flarion is proprietary and not downloadable (the page says contact us), and no repository or scripts were found for its benchmarks. A published list of supported Spark versions: none found on 2026-11-10. Third-party benchmarks of Flarion: none found on 2026-11-10. |
| Published speed results | 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. | The home page headline is 'Run faster, spend less, scale further, without changing a line of code', with tiles for 6 minute setup, 3x performance gains and 60% cost reduction. The tiles carry no workload or method on the page. The benchmarks page (September 2026) compares six engines on TPC-DS (103 queries) on one i4i.8xlarge reading Parquet from S3. Flarion is faster than vanilla Spark, Comet and Gluten, and slower than Databricks Photon in both scales. At 100 GB: Spark 1,135 s, Flarion 386 s, Photon 362 s. At 1 TB: Spark 135.6 min, Flarion 38.3 min, Photon 30.4 min. The page labels these as benchmark figures, not customer results, and not an audited TPC result. |
| Published cost results and prices | 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. | Usage-based list prices: self-hosted Spark on AWS, Azure or GCP $0.009 per CPU hour; fully managed Spark (EMR, GCP managed Spark, Azure HDInsight) $0.012 per CPU hour; Databricks $0.095 per DBU; on-premises $0.75 per CPU per month. Billing is on accelerated Spark cores (driver plus executors). A free assessment simulates each job from logs and reports projected runtime and compute. |
| Code changes | 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. | Flarion is one JAR inside the existing cluster, with no agents or separate services. UDFs and UDAFs run on Spark as before. Operations Flarion does not accelerate run on Spark automatically. The page lists a 'one config change' install and says you can turn it off with one config change to compare. |
| Tuning | 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. | The FAQ says existing Spark tuning carries over and is kept; Flarion changes how the engine executes. The garbage-collection post says native memory is managed off-heap with no GC pauses, but part of a job (driver, planning, unsupported operators, often the final write) still runs on the JVM heap. Telemetry marks each stage native or Spark with runtime and memory. |
| Spark versions, platforms and table formats | 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. | Platforms listed: Databricks (init scripts), Amazon EMR (bootstrap action), Google Cloud Dataproc, Azure HDInsight, Spark on Kubernetes (Helm chart or Spark operator) and on-premises. Frameworks: Scala Spark, PySpark, Trino, Ray. Table formats: Iceberg, Delta Lake, Hudi. File formats: Parquet, Avro, JSON. The benchmark ran Spark 3.5.5 and Databricks 16.4 LTS (Spark 3.5.2). A supported-version list is not published; a blog post mentions staying on Spark 3.4 and gaining newer-Spark benefits. |
| Where it runs | 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. | No special hardware: Flarion runs CPU-native on the fleet already in use (FAQ contrasts it with GPU accelerators). It is usable on AWS, Azure, GCP, on-premises and air-gapped setups. The company is SOC 2 Type II certified per the home page. |
| How open its benchmarks are | 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. | The benchmark page publishes the machine, Spark 3.5.5 baseline, engine builds (Comet 1.0.0, Gluten 1.7.0 Velox, Databricks DBR 16.4 LTS), memory budgets, shuffle partitions (64), AQE on, no statistics/CBO, per-query caps (600 s at 100 GB, 1,800 s at 1 TB) and lower of two runs at 100 GB and one run at 1 TB. It discloses that q72 is counted at vanilla Spark's time for Gluten and Comet. It says the open-source engines can be rerun from public releases, but Flarion itself is not downloadable ('contact us'), and no repo or scripts were found. |
| Change Budget: 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. | No code change stated. Flarion says UDFs and UDAFs run on Spark as before and operations it does not accelerate run on Spark automatically. The home page headline says 'without changing a line of code'. |
| Change Budget: cluster | Set runtime_engine to PHOTON in API. 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. | One JAR and one config change. Flarion is one JAR inside the existing cluster, installed with a one config change and switched off with one config change. Existing Spark tuning carries over. |
| Change Budget: cloud | Databricks on AWS, Azure or GCP. Photon is documented as part of Databricks compute on AWS, Azure and Google Cloud. | No single cloud required. Flarion lists Databricks, Amazon EMR, Google Cloud Dataproc, Azure HDInsight, Spark on Kubernetes and on-premises, and says it supports air-gapped setups. |
| Change Budget: vendor | Databricks platform required. 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. | Flarion license at usage-based prices. Flarion lists $0.009 per CPU hour (self-hosted), $0.012 (fully managed Spark), $0.095 per DBU (Databricks) and $0.75 per CPU per month (on premises), billed on accelerated Spark cores. |
| Ledger entries | Photon customer speedups, SIGMOD 2022 paper (run by its maker); Databricks audited 100 TB TPC-DS result on Photon (run by its maker) | Flarion TPC-DS SF100, six engines on one machine (run by its maker); Flarion TPC-DS SF1000, six engines on one machine (run by its maker) |
How to read this page
The rows hold what each vendor or a named third party published, with no conclusion drawn. Benchmarks in the two columns were run on different hardware, data and baselines unless the Ledger entry says otherwise, so the numbers are not comparable across columns. The Ledger method explains how entries are recorded.
Sources
- Databricks Photon: docs.databricks.com/en/compute/photon.html, read 10 Nov 2026
- Databricks Photon: databricks.com/product/pricing, read 10 Nov 2026
- Databricks Photon: people.eecs.berkeley.edu/~matei/papers/2022/sigmod_photon.pdf, read 10 Nov 2026
- Databricks Photon: databricks.com/blog/2021/11/02/databricks-sets-official-data-warehousing, read 10 Nov 2026
- Flarion: flarion.io, read 10 Nov 2026
- Flarion: flarion.io/benchmarks, read 10 Nov 2026
- Flarion: flarion.io/pricing, read 10 Nov 2026
- Flarion: flarion.io/faqs, read 10 Nov 2026
- Flarion: flarion.io/product, read 10 Nov 2026
Last reviewed 10 Nov 2026.