Side by side, read 10 Nov 2026
DualBird and Open stack on EMR and EKS: the published facts in the same rows
DualBird profileOpen stack on EMR and EKS profile
The same rows for both
| Row | DualBird | Open stack on EMR and EKS |
|---|---|---|
| Kind | FPGA Spark plugin for AWS F2 | Self-run Spark with open table formats |
| Does well | 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. | Per AWS documentation, EMR 7.14.0 packages Spark 3.5.8-amzn-0, Delta 3.3.2-amzn-3, Iceberg 1.10.1-amzn-1 and Hudi 1.0.2-amzn-3, so all three formats are available (read 2026-11-10). AWS ran TPC-DS 3 TB on 9 x r5d.4xlarge and reports $4.81 for EMR 7.12 against $17.65 for open-source Spark 3.5.6 with Iceberg 1.10.0, with repositories to repeat it. |
| Limited | 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. | Per the Apache Iceberg documentation, users run table maintenance themselves: expire snapshots, remove orphan files and compact with rewriteDataFiles as jobs they schedule (read 2026-11-10). A cost comparison of open-stack Spark against managed lakehouses by a party other than AWS or a vendor: none found on 2026-11-10. |
| Published speed results | 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. | AWS ran TPC-DS 3 TB (104 SparkSQL queries, 3 rounds, 9 x r5d.4xlarge, Hadoop catalog) and reports EMR 7.12 averaged 1,349.62 s versus 6,113.92 s for open-source Spark 3.5.6 with Iceberg 1.10.0 and 1,535.62 s for EMR 7.5. AWS notes results are not comparable to official TPC-DS. The run is by the vendor of EMR. |
| Published prices and cost results | 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. | EMR on EC2 charges an EMR price in addition to the EC2 price (and EBS), billed per second with a one-minute minimum. AWS's example in us-east-1: c4.2xlarge EMR charge $0.105/hour next to EC2 $0.398/hour; one master and two core nodes for a month total $1,101.57. Spot instances are up to a 90% discount versus On-Demand. EMR on EKS adds an uplift per vCPU-hour and per GB-hour to EKS/EC2 or Fargate costs, plus $0.10 per hour for each EKS cluster. AWS's worked example uses $0.007084 per vCPU-hour and $0.000777875 per GB-hour (100 vCPU and 300 GB for 30 minutes = $0.4709 EMR uplift). The uplift applies to any pod using an EMR runtime image, including with the Spark operator. EMR Serverless is billed per vCPU-hour and GB-hour. AWS's worked example uses $0.052624 per vCPU-hour and $0.0057785 per GB-hour for a job with 100 vCPU and 750 GB for 30 minutes, then 200 more vCPU for 15 minutes, totaling $9.596275. In the same AWS benchmark the cost was $4.81 for EMR 7.12, $5.47 for EMR 7.5 and $17.65 for open-source Spark 3.5.6 with Iceberg 1.10.0. Cost formula uses r5d.4xlarge at $1.152/hour plus $0.27/hour EMR plus EBS, On-Demand. |
| Code changes and migration | 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. | The EMR runtime for Spark provides 'full API compatibility with open source Apache Spark and Apache Iceberg', so existing Spark jobs run as is. Optimized runtimes are used by EMR on EC2, EMR Serverless, EMR on EKS, EMR on Outposts and AWS Glue. Self-run Spark on EKS uses the open-source Spark operator and needs no job rewrite. |
| Tuning and table upkeep | 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. | Iceberg docs say users must run maintenance: expire snapshots, remove old metadata files and delete orphan files are 'recommended'; compacting data files with the Spark rewriteDataFiles action (for example target-file-size-bytes of 500 MB) and rewriting manifests are 'optional' maintenance, run as jobs you schedule. Hudi merge-on-read tables need compaction to merge log files into base files and bound read latency. Compaction has two steps, scheduling (plan written to the timeline) and execution; the docs describe strategies for choosing which file slices to compact. Delta Lake OSS docs list file management features the user applies: compaction (bin-packing) with OPTIMIZE, auto compaction, data skipping, Z-ordering, multi-part checkpointing, log compactions and optimized write. |
| Spark versions and table formats | 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'). | Amazon EMR 7.14.0 packages Spark 3.5.8-amzn-0, Delta 3.3.2-amzn-3, Iceberg 1.10.1-amzn-1 and Hudi 1.0.2-amzn-3. All three table formats are available on EMR. EMR on EKS supports the Kubernetes Operator for Apache Spark (Spark operator) as a job submission model with the EMR runtime on your own EKS clusters. The Kubeflow Spark Operator is Apache-2.0 licensed with Helm installation. |
| Where it runs | 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'. | Amazon EMR has regional endpoints in the US (us-east-1, us-east-2, us-west-1, us-west-2) and many other AWS regions per the AWS general reference endpoints table. Spark runs on EC2 instances the user chooses (the AWS benchmark used r5d.4xlarge). |
| How open its benchmarks are | 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). | AWS publishes the setup in GitHub repositories (aws-samples/emr-on-eks-benchmark branch tpcds-v2.13_iceberg, and aws-samples/emr-spark-benchmark) with build instructions, so the TPC-DS Iceberg benchmark can be repeated. |
| Compute Bill | DualBird on Amazon EMR (F2 instances): $49.50 | Open stack: Spark on plain EC2: $20.16 |
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
- 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
- Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: aws.amazon.com/emr/pricing, read 10 Nov 2026
- Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: aws.amazon.com/blogs/big-data/run-apache-spark-and-iceberg-4-5x-faster-t, read 10 Nov 2026
- Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-release-app-versions-7.x, read 10 Nov 2026
- Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/spark-operato, read 10 Nov 2026
- Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: iceberg.apache.org/docs/latest/maintenance, read 10 Nov 2026
- Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: hudi.apache.org/docs/compaction, read 10 Nov 2026
- Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: docs.delta.io/latest/optimizations-oss.html, read 10 Nov 2026
- Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: docs.aws.amazon.com/general/latest/gr/emr.html, read 10 Nov 2026
- Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: github.com/aws-samples/emr-on-eks-benchmark, read 10 Nov 2026
Last reviewed 10 Nov 2026.