Side by side, read 10 Nov 2026
Databricks and Dremio: the published facts in the same rows
Databricks profileDremio profile
The same rows for both
| Row | Databricks | Dremio |
|---|---|---|
| Kind | Managed lakehouse built around Delta Lake | Lakehouse with its own SQL engine |
| Does well | Per Databricks documentation, Photon keeps the Spark Catalyst planner, works with existing Spark API code and falls back to the Spark runtime for unsupported operations (read 2026-11-10). Per Databricks documentation, Delta tables can generate Iceberg metadata from Runtime 14.3 LTS, so Iceberg clients read Delta data without rewriting files (read 2026-11-10). | Per Dremio documentation, Iceberg tables in the Open Catalog get automatic optimization: data file compaction, row-level delete handling, clustering, partition evolution and manifest rewriting (read 2026-11-10). Dremio publishes DCU rates by engine size, from 16 DCUs per hour for 2XSmall to 2048 for 3XLarge, with a 60-second minimum (read 2026-11-10). |
| Limited | Per Databricks documentation, serverless compute supports only Spark Connect APIs, so RDD APIs, R and Maven coordinates are unsupported, and ANSI mode on by default can change results of existing jobs. Per Databricks, compute is billed in DBUs in addition to the cloud bill for the same instances, so a Jobs Compute run pays Databricks and AWS separately; the Compute Bill line adds $12.24 of DBUs to $20.16 of EC2 (read 2026-11-10). | Per Dremio documentation, queries run on its own columnar engine, not on Spark, and the pages read describe no mode that runs existing Spark jobs. Dremio Cloud documentation lists Iceberg and Delta Lake as table formats; Hudi support: none found on 2026-11-10. |
| Published speed results | Docs claim Photon gives up to 5x better price/performance for data and analytics workloads versus other cloud data warehouses; no method is given on this page. Databricks announced an audited 100TB TPC-DS result of 32,941,245 QphDS for Databricks SQL, 2.2x the previous record held by Alibaba, with total system cost 10% lower on list pricing. This is a SQL warehouse result, not a Spark batch ETL result. The same Databricks blog says research from Barcelona Supercomputing Center found Databricks 2.7x faster and 12x better in price-performance than Snowflake on a TPC-DS derivative. This is a vendor-reported claim of a third-party study; the study itself was not fetched. | Dremio's founder reported a full 1 TB TPC-DS run (all 99 queries) in 22 seconds on an 8-node m7gd.4xlarge cluster, with no caching, and attributes it to Autonomous Reflections and automatic Iceberg clustering. This is a BI query benchmark run by the vendor, not a Spark batch ETL or compaction test. |
| Published prices and cost results | Databricks bills compute in DBUs at per-second granularity with pay-as-you-go or committed-use discounts, and no up-front costs. The pricing pages render their rates by script; the AWS pricing data file those pages load lists Jobs Compute at $0.15 per DBU on the plan it names Premium (r6i.4xlarge: 4.08 DBU per hour). The file names no region. Jobs pricing offers serverless (Performance Optimized and Standard modes) and classic clusters; the jobs pricing page maps plan names across clouds (its Premium tier on Azure corresponds to Enterprise on AWS and GCP), while the AWS pricing data file lists the $0.15 Jobs Compute rate under a plan it names Premium. Photon instances consume DBUs at a different rate. | Dremio Cloud is priced at $0.20 per DCU (Dremio Compute Unit). Dremio Enterprise (self-managed) pricing is 'contact sales'. The free trial for Dremio Cloud is a $400 credit for 30 days. DCUs are consumed only while engines run. Usage equals engine and replica uptime in seconds (60-second minimum) times the DCU rate for the engine size. Published rates per hour: 2XSmall 16, XSmall 32, Small 64, Medium 128, Large 256, XLarge 512, 2XLarge 1024, 3XLarge 2048. Storage billed in TB-months only for Dremio-hosted storage; LLM tokens billed separately. Billable usage is DCUs (compute), LLM tokens (AI features) and storage. Compute is billed in DCUs only while engines are running. |
| Code changes and migration | Photon is a native C++ vectorized engine that keeps Spark's Catalyst planner and works with existing Spark API code; unsupported operations fall back to the Spark runtime. Serverless compute for notebooks and jobs supports only Spark Connect APIs; Spark RDD APIs, R, Maven coordinates, global temp views, DBFS mounts with instance profiles and Databricks Container Services are not supported. ANSI mode is on by default and the default time zone is UTC, which can change results of existing jobs. | Dremio runs queries on its own columnar execution engine built on Apache Arrow, not on Spark. Docs describe Spark and Flink only as external engines that can use the Open Catalog (Iceberg REST) alongside Dremio. The pages read describe no mode that runs existing Spark jobs, so Spark ETL would stay on Spark or be rewritten as Dremio SQL. |
| Tuning and table upkeep | Photon is on by default for classic all-purpose compute, jobs compute and classic pipelines; API users must set runtime_engine to PHOTON. Photon instance types use DBUs at a different rate than the same instance without Photon. On serverless compute Databricks allocates and manages compute so users do not provision clusters; the Spark UI and Spark logs are not available, query profile and client-side logs are used instead. Serverless compute runs workloads without provisioning compute in your cloud account, and Databricks says this reduces the need to manage compute resources. It requires Unity Catalog to reach external data sources. | For Iceberg tables in the Open Catalog, Dremio runs automatic optimization on a dedicated engine it configures: data file compaction, row-level delete handling (position deletes on v2, deletion vectors on v3), clustering, partition evolution and manifest rewriting. The same operations can be run by hand with OPTIMIZE TABLE. Optimization works in batches sized to engine resources. Engines have settings the admin chooses: size (executors per replica), min and max replicas, last-replica auto-stop (default 2 hours), enqueued time limit (default 5 minutes) and query runtime limit. Default concurrency per replica ranges from 2 (2XSmall) to 20 (3XLarge). |
| Spark versions and table formats | Databricks Runtime 18 LTS ships Apache Spark 4.1.0 (released June 10, 2026); Runtime 17.3 LTS ships Spark 4.0.0; Runtime 16.4 LTS and 15.4 LTS ship Spark 3.5.x. Runtime 19 ships Spark 4.2.0 (July 23, 2026). Delta Lake tables can generate Iceberg metadata (UniForm, Iceberg reads) from Databricks Runtime 14.3 LTS so Iceberg clients read Delta data without rewriting files. | The Dremio Cloud data formats page lists Apache Iceberg and Delta Lake as table formats (plus Parquet and text formats). Hudi is not listed on that page. The Open Catalog is built on Apache Polaris and supports the Iceberg REST Catalog API; the docs list AWS Glue Data Catalog as a connectable catalog. |
| Where it runs | Databricks on AWS lists many AWS regions including us-east-1 (US East, Northern Virginia), us-east-2, us-west-1, eu-west-1, eu-central-1, ap-southeast-2 and us-gov-west-1; the platform is also hosted on Azure and Google Cloud. Some features are only in a subset of regions. | Dremio Cloud runs on AWS (Azure listed as coming soon). Supported regions: us-east-1, us-east-2, us-west-2, eu-west-1 and eu-central-1. Dremio Enterprise can be deployed on Kubernetes, on premises, or in AWS, Azure or GCP. |
| How open its benchmarks are | None found on 10 Nov 2026. | Dremio published a 2020 TPC-DS methodology post (SF1000 and SF10000, Parquet on S3, Apache JMeter test plans, 58 of 99 queries that ran unmodified on Dremio and Presto distributions). The 2025 22-second TPC-DS post pages read give cluster type but no scripts, scale-factor files or configuration repository. |
| Compute Bill | Databricks on AWS (Jobs Compute): $32.40 | Dremio Cloud (Large engine): $102.40 |
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 ran on different hardware, data and baselines, so their numbers are not comparable across columns. The Compute Bill method explains the cost lines.
Sources
- Databricks Data Intelligence Platform on AWS: docs.databricks.com/aws/en/compute/photon, read 10 Nov 2026
- Databricks Data Intelligence Platform on AWS: docs.databricks.com/aws/en/compute/serverless/limitations, read 10 Nov 2026
- Databricks Data Intelligence Platform on AWS: docs.databricks.com/aws/en/compute/serverless, read 10 Nov 2026
- Databricks Data Intelligence Platform on AWS: docs.databricks.com/aws/en/release-notes/runtime, read 10 Nov 2026
- Databricks Data Intelligence Platform on AWS: docs.databricks.com/aws/en/delta/uniform, read 10 Nov 2026
- Databricks Data Intelligence Platform on AWS: docs.databricks.com/aws/en/resources/supported-regions, read 10 Nov 2026
- Databricks Data Intelligence Platform on AWS: databricks.com/blog/2021/11/02/databricks-sets-official-data-warehousing, read 10 Nov 2026
- Databricks Data Intelligence Platform on AWS: databricks.com/product/aws-pricing, read 10 Nov 2026
- Databricks Data Intelligence Platform on AWS: databricks.com/product/pricing/jobs, read 10 Nov 2026
- Dremio: dremio.com/pricing, read 10 Nov 2026
- Dremio: docs.dremio.com/dremio-cloud/admin/engines, read 10 Nov 2026
- Dremio: docs.dremio.com/dremio-cloud/admin/subscription/usage, read 10 Nov 2026
- Dremio: docs.dremio.com/current/what-is-dremio/architecture, read 10 Nov 2026
- Dremio: docs.dremio.com/dremio-cloud/developer/data-formats, read 10 Nov 2026
- Dremio: docs.dremio.com/dremio-cloud/manage-govern/optimization, read 10 Nov 2026
- Dremio: docs.dremio.com/dremio-cloud/about/regions, read 10 Nov 2026
- Dremio: dremio.com/blog/breakthrough-announcement-dremio-is-the, read 10 Nov 2026
- Dremio: dremio.com/blog/dremio-benchmarking-methodology, read 10 Nov 2026
Last reviewed 10 Nov 2026.