Side by side, read 10 Nov 2026
Apache Auron and DualBird: the published facts in the same rows
Apache Auron profileDualBird profile
The same rows for both
| Row | Apache Auron | DualBird |
|---|---|---|
| Kind | Open-source Rust engine plugin for Spark | FPGA Spark plugin on AWS F2 |
| Does well | The project publishes its TPC-DS 1 TB method, with data generation and runner tools in the auron-project/tpcds-tools repository and the full Spark configuration. Its build script lists Spark 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 4.0, 4.1 and 4.2 with Scala 2.12 and 2.13. | DualBird publishes a worked example: a sort-based Iceberg compaction benchmark on 100 GB, with the dataset shape (about 370 million rows, 64 columns, ZSTD level 3) and two baselines (vanilla Spark and an unnamed C++ accelerated Spark). DualBird says onboarding is an instance type change to F2 plus its Spark plugin, and that Spark still handles planning, scheduling and fault tolerance. |
| Limited | You build the jar yourself (Rust nightly and a JDK are required), and the getting-started page describes building from source. Support for Amazon EMR, EKS or Databricks: none found on 2026-11-10 in the project's pages. The benchmark's per-query results are published as a chart image only. | DualBird runs on AWS F2 instances only, so it is not an option on Azure, Google Cloud or a Databricks-managed cluster, and every benchmark published for it so far is its own. F2 is listed in eight AWS regions (not, for example, us-east-2 or eu-west-1), the method for its compaction benchmark is behind a sign-up form, and no price for the plugin is published. A DualBird engineer states that workloads dominated by Python UDFs or unsupported operators fall back to the CPU and do not see the same benefit yet. |
| Published speed results | The project says it has passed all TPC-DS and TPC-H cases and, compared with Spark 3.5, runs about 2x faster and saves about 50% of cluster resources. The only published detail is the TPC-DS 1 TB benchmark page; no per-query numbers are in text form (results are a chart). | 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 cost results and prices | None found on 10 Nov 2026. | 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 | Auron is added by putting a jar on the Spark classpath and setting spark.auron.enable, the AuronSparkSessionExtension and the AuronShuffleManager; no job changes. The project describes fine-grained fallback for unsupported operators, and the Spark UI has an Auron tab that records per-operator fallback reasons. You must build the jar yourself (Rust nightly and JDK required); the getting-started page describes building from source. | 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 | The suggested config disables Spark off-heap memory and moves memory into executor overhead (4096 MB in the quick start). The benchmark used executor memory 8g with overhead 16384 for Auron versus 20g with 4096 for plain Spark, plus spark.auron.memoryFraction 0.8, forceShuffledHashJoin and sort-merge-join and UDAF fallback settings. ORC with large string/binary values needs spark.auron.orc.batchSize lowered. | 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, platforms and table formats | The build script lists supported Spark versions 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 4.0, 4.1 and 4.2 with Scala 2.12 and 2.13, and Celeborn 0.5/0.6 and Uniffle 0.10 remote shuffle. The 8.0.0 notes add Spark 4.0 and 4.1 build support. No EMR, EKS or Databricks support is documented. The 8.0.0-incubating release notes say it added and expanded native scan support for Apache Iceberg, Apache Hudi and Apache Paimon, including Copy-on-Write tables and Iceberg changelog scans. The homepage says it supports Hudi and Paimon. 8.0.0 also adds Flink integration. Delta Lake is not mentioned in the fetched pages. | 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 | Build needs Rust nightly and JDK; the README says regularly tested on JDK 8, 11 and 17 and also on JDK 21. The build script supports OS images centos7, ubuntu24, rockylinux8, debian11 and azurelinux3, and macOS builds were added in 8.0.0. The homepage says it supports storage such as HDFS and S3. No cloud-specific instance guidance was found. | 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 | The benchmark page publishes the method end to end: TPC-DS 1 TB data generated with a datagen tool (derived from maropu/spark-tpcds-datagen) and run with a benchmark runner (derived from databricks/spark-sql-perf), both in the auron-project/tpcds-tools repo, with the full Spark config. It ran Spark 3.5.6 against Auron 6.0.0-preview on YARN. Node types and counts are not given (the config shows executor cores 8 and a very large maxExecutors). | 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). |
| Change Budget: code | No job code change stated. Auron is added with a jar on the Spark classpath and three settings (spark.auron.enable, the AuronSparkSessionExtension and the AuronShuffleManager); the project states no job changes. | No code change stated. DualBird's about page says 'No infrastructure changes. No code changes.' |
| Change Budget: cluster | Build the jar, set three configs. You must build the jar yourself (Rust nightly and a JDK). The quick start disables Spark off-heap memory and moves memory into executor overhead (4096 MB). | Instance type change to F2. DualBird's onboarding is two changes: switch the EC2 instance type to F2 and add the DualBird Spark plugin. Cluster sizing then reduces to the number of F2 nodes, per DualBird. |
| Change Budget: cloud | None found on 2026-11-10. No cloud requirement is stated. The homepage says it supports storage such as HDFS and S3, and no cloud-specific instance guidance was found. Documented support for EMR, EKS or Databricks: none found on 2026-11-10. | AWS only, F2 in eight regions. F2 is listed in us-east-1, us-west-2, ap-northeast-1, ap-northeast-2, ap-southeast-2, ca-central-1, eu-central-1 and eu-west-2, and not, for example, in us-east-2 or eu-west-1. DualBird mentions no other cloud. |
| Change Budget: vendor | Apache-2.0, no contract stated. Auron is Apache-2.0 licensed under the Apache Software Foundation; no vendor or platform contract is described. | Plugin contract; no price published. No pricing, price list or marketplace listing was found on DualBird's site, and the pricing model for the plugin is not stated. |
| Ledger entries | Auron TPC-DS 1 TB against Apache Spark 3.5.6 (run by its maker) | DualBird sort-based Iceberg compaction, 100 GB (run by its maker); DualBird 110 GB enrichment pipeline (join denormalization) (run by its maker); DualBird single task performance tile (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
- Apache Auron (incubating), formerly Blaze: auron.apache.org, read 10 Nov 2026
- Apache Auron (incubating), formerly Blaze: auron.apache.org/documents/benchmarks.html, read 10 Nov 2026
- Apache Auron (incubating), formerly Blaze: raw.githubusercontent.com/apache/auron/master/auron-build.sh, read 10 Nov 2026
- Apache Auron (incubating), formerly Blaze: auron.apache.org/archives/v8.0.0-incubating.html, read 10 Nov 2026
- Apache Auron (incubating), formerly Blaze: raw.githubusercontent.com/apache/auron/master/README.md, read 10 Nov 2026
- DualBird: dualbird.io, read 10 Nov 2026
- DualBird: dualbird.io/product, read 10 Nov 2026
- DualBird: dualbird.io/resources/blog/a-simpler-spark, read 10 Nov 2026
- DualBird: dualbird.io/resources/blog/iceberg-compaction-benchmark-faster-spark-low, read 10 Nov 2026
- DualBird: dualbird.io/resources/blog/spark-iceberg-compaction-benchmark-whitepaper, read 10 Nov 2026
- DualBird: aws.amazon.com/ec2/instance-types/f2, read 10 Nov 2026
- DualBird: docs.aws.amazon.com/ec2/latest/instancetypes/ec2-instance-regions.html, read 10 Nov 2026
- DualBird about page, read 10 Nov 2026
Last reviewed 10 Nov 2026.