# Dremio and DualBird: the published facts in the same rows

Side by side, read 10 Nov 2026

**The short answer.** Dremio (Lakehouse with its own SQL engine) and DualBird (FPGA Spark plugin for AWS F2) are set out here in the same rows: published speed and cost results, code changes, table upkeep, table formats and where each runs. On the Compute Bill's reference job: Dremio Cloud (Large engine): $102.40; DualBird on Amazon EMR (F2 instances): $49.50.

## The same rows for both

| Row | Dremio | DualBird |
| --- | --- | --- |
| Kind | Lakehouse with its own SQL engine | FPGA Spark plugin for AWS F2 |
| Does well | 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). | DualBird says onboarding is two changes: switch the EC2 instance type to F2 and add the DualBird Spark plugin, with Spark still handling planning and scheduling (read 2026-11-10). DualBird published a 100 GB sort-based Iceberg compaction run on June 11, 2026, run by DualBird, and states about $2 per TB for itself against about $6 per TB for CPU clusters. |
| Limited | 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. | DualBird is not a lakehouse. It speeds up Spark on EMR and EKS; a team on a fully managed platform cannot add it. It documents no Spark version list and no table-format support list; Iceberg appears only in its own compaction benchmark. A price for the plugin and a benchmark run by a party other than DualBird: none found on 2026-11-10. |
| Published speed results | 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. | The home page body text states the headline claim as 10x-30x faster data processing with 50%-90% lower costs and no changes required. The same wording appears in the page's JSON-LD organization description and in the April 28, 2026 blog post. The raw HTML of the home page has a different range in its meta description and og:description (and twitter:description): 10x-100x faster. This is the meta tag, not body text. The February 5, 2026 funding blog post also says 10-100x faster and 50-90% cost savings. The body text of the home and product pages says 10x-30x, so the two ranges differ by site location. The product page repeats the 10x-30x end-to-end figure labeled 'Instance for instance' and 50%-90% cost reduction labeled 'Workload for workload'. The meta description of the product page is only 'Plug-and-play Spark acceleration.' Home and product pages show a '110GB Enrichment Pipeline (JOIN Denormalization)' benchmark: 50%-85% lower EC2 cost with 6x-18x higher performance ceiling. The pages give no hardware, baseline, dates or method, and no link to a write-up was found. Sort-based Iceberg compaction on 100 GB, compared with vanilla Spark and with an unnamed 'C++ accelerated Spark' (unnamed) with tuned EBS, memory and parallelism at each cluster size. Dataset is synthetic: about 370 million rows, 64 mixed-type columns, ZSTD level 3. Results: roughly 12-20x faster single-task execution, 55-85% lower EC2 cost, stable cost across scaling, about 6x higher practical performance ceiling. Cost per terabyte compacted is stated as about $2/TB for DualBird versus about $6/TB rising past $13/TB for CPU clusters. Part of the saving is attributed to F2 local NVMe replacing EBS volumes. The home page shows 'X15-X20' single-task speedup for the same benchmark, while the June 11, 2026 blog and the white paper landing page say 12-20x. The two do not match. The 'Single Task Performance' home-page tile says X15-X20 speedup for the same cluster size while reducing cost by over 50%. The blog describes the single-task comparison as against vanilla Spark, and the April 28 post as against 'a high-end C++ columnar engine running on a single CPU core'. The baseline wording is therefore not consistent across pages. |
| Published prices and cost results | 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. | No pricing, price list or marketplace listing was found on the site. Cost claims are only percentages (50%-90% lower, 55%-85% lower EC2) and the about $2/TB versus $6-13/TB compaction figure. The pricing model for the plugin itself is not stated, so users cannot tell whether F2 instance price or license fee is included in the claimed savings. |
| Code changes and migration | 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. | Onboarding is two changes: switch the EC2 instance type to F2 and add the DualBird Spark plugin. The page shows three steps: change instance type, use our Spark plugin, see the results. The about page says 'No infrastructure changes. No code changes.' The compaction blog says Spark still handles planning, scheduling and fault tolerance and no pipeline rewrite or platform migration is needed. A DualBird engineer states the FPGA path accelerates a defined set of operators (sort, join, aggregation and others). Workloads dominated by Python UDFs or unsupported operators fall back to CPU and do not see the same benefit yet. Coverage is described as expanding. |
| Tuning and table upkeep | 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). | DualBird claims tens of Spark settings (executor sizing, CPU-memory ratios, parallelism) become irrelevant, disk spills effectively disappear and data skew stops causing spills, because only a few tasks run at once on the FPGA. The product page says the majority of common Spark performance configurations do not exist when using the solution. Cluster sizing reduces to the number of F2 nodes. These are vendor claims, not independently tested. Part 2 of the series (Sep 1, 2026) says skew still costs time, but less, and that it does not need repartitioning or salting. |
| Spark versions and table formats | 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. | The home page says the plugin is compatible with Apache Spark, Amazon EMR and Amazon EKS. It lists 'Optimized out of the box', 'Migration-free' and 'No more performance tuning and troubleshooting'. No Spark version numbers, Databricks support or Iceberg/Delta/Hudi support list are stated on the home, product, about or resources pages. Iceberg appears only in the compaction benchmark and in the meta description of the Dec 1, 2025 demo post ('Accelerate Apache Spark and Apache Iceberg'). |
| Where it runs | 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. | DualBird needs AWS EC2 F2 instances. AWS describes F2 as second-generation FPGA instances with up to 8 AMD Virtex UltraScale+ HBM VU47P FPGAs, 16 GiB HBM per FPGA, 3rd-gen AMD EPYC (Milan) CPUs up to 192 vCPU, up to 2 TiB memory and up to 7.6 TiB NVMe. Sizes: f2.6xlarge (1 FPGA, 24 vCPU, 256 GiB), f2.12xlarge (2 FPGAs, 48 vCPU, 512 GiB), f2.48xlarge (8 FPGAs, 192 vCPU, 2,048 GiB). The AWS 'instance types by Region' doc lists F2 in eight regions: us-east-1 (N. Virginia), us-west-2 (Oregon), ap-northeast-1 (Tokyo), ap-northeast-2 (Seoul), ap-southeast-2 (Sydney), ca-central-1 (Canada Central), eu-central-1 (Frankfurt) and eu-west-2 (London). F2 is not listed in other regions on that page (for example us-east-2, eu-west-1). DualBird is AWS-only: no other cloud is mentioned. The product page says deployment runs on the customer's own servers in their AWS environment and 'Everything stays under your control'. |
| How open its benchmarks are | 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. | The white paper (dated July 1, 2026) has a landing page that restates the results and says methodology, system architecture and detailed analysis are in a download. The full document is gated behind a form and was not readable. The blog gives dataset shape and baselines but not instance counts, Spark version, configs or scripts. No public repo was found (github.com/dualbird returns 404). |
| Compute Bill | Dremio Cloud (Large engine): $102.40 | DualBird on Amazon EMR (F2 instances): $49.50 |

Alphabetical order. Vendor statements are the vendor's own. Read 10 Nov 2026.

## 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](/compute-bill/method/) explains the cost lines.

## Sources

- Dremio: dremio.com/pricing: https://www.dremio.com/pricing (read 10 Nov 2026)
- Dremio: docs.dremio.com/dremio-cloud/admin/engines: https://docs.dremio.com/dremio-cloud/admin/engines/ (read 10 Nov 2026)
- Dremio: docs.dremio.com/dremio-cloud/admin/subscription/usage: https://docs.dremio.com/dremio-cloud/admin/subscription/usage (read 10 Nov 2026)
- Dremio: docs.dremio.com/current/what-is-dremio/architecture: https://docs.dremio.com/current/what-is-dremio/architecture (read 10 Nov 2026)
- Dremio: docs.dremio.com/dremio-cloud/developer/data-formats: https://docs.dremio.com/dremio-cloud/developer/data-formats/ (read 10 Nov 2026)
- Dremio: docs.dremio.com/dremio-cloud/manage-govern/optimization: https://docs.dremio.com/dremio-cloud/manage-govern/optimization (read 10 Nov 2026)
- Dremio: docs.dremio.com/dremio-cloud/about/regions: https://docs.dremio.com/dremio-cloud/about/regions (read 10 Nov 2026)
- Dremio: dremio.com/blog/breakthrough-announcement-dremio-is-the: https://www.dremio.com/blog/breakthrough-announcement-dremio-is-the-fastest-lakehouse-20x-faster-on-tpc-ds/ (read 10 Nov 2026)
- Dremio: dremio.com/blog/dremio-benchmarking-methodology: https://www.dremio.com/blog/dremio-benchmarking-methodology/ (read 10 Nov 2026)
- DualBird: dualbird.io: https://dualbird.io/ (read 10 Nov 2026)
- DualBird: dualbird.io/product: https://dualbird.io/product (read 10 Nov 2026)
- DualBird: dualbird.io/resources/blog/a-simpler-spark: https://dualbird.io/resources/blog/a-simpler-spark (read 10 Nov 2026)
- DualBird: dualbird.io/resources/blog/iceberg-compaction-benchmark-faster-spark-low: https://dualbird.io/resources/blog/iceberg-compaction-benchmark-faster-spark-lower-cost (read 10 Nov 2026)
- DualBird: dualbird.io/resources/blog/spark-iceberg-compaction-benchmark-whitepaper: https://dualbird.io/resources/blog/spark-iceberg-compaction-benchmark-whitepaper (read 10 Nov 2026)
- DualBird: aws.amazon.com/ec2/instance-types/f2: https://aws.amazon.com/ec2/instance-types/f2/ (read 10 Nov 2026)
- DualBird: docs.aws.amazon.com/ec2/latest/instancetypes/ec2-instance-regions.html: https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-instance-regions.html (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalakehousecompare.com/compare/dremio-vs-dualbird/
