# DualBird and Google BigQuery and BigLake: the published facts in the same rows

Side by side, read 10 Nov 2026

**The short answer.** DualBird (FPGA Spark plugin for AWS F2) and Google BigQuery and BigLake (Serverless Google Cloud data warehouse) 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: DualBird on Amazon EMR (F2 instances): $49.50; BigQuery (Enterprise edition slots): $19.20.

## The same rows for both

| Row | DualBird | Google BigQuery and BigLake |
| --- | --- | --- |
| Kind | FPGA Spark plugin for AWS F2 | Serverless Google Cloud data warehouse |
| 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 Google documentation, BigQuery Iceberg managed tables store data in buckets you own, support DML and streaming, and run automatic compaction, clustering and garbage collection (read 2026-11-10). Per Google documentation, stored procedures for Apache Spark run PySpark or Scala/Java JAR code from SQL on Google Cloud (read 2026-11-10). |
| 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 Google documentation, BigQuery Omni on S3 does not support DML or CREATE TABLE, so it does not run write-heavy Spark batch ETL on S3. Google's pricing page text lists Enterprise edition compute at $0.06 per slot-hour, with no region shown beside the rate (read 2026-11-10). Per-TiB on-demand and Spark DCU rates are not used on this site. |
| 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. | Google states Lightning Engine delivers up to 4.9x faster performance than open source Spark and up to 2.5x the price-performance over a high-speed Spark offering Google does not name; no method is given on the pricing page. |
| 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. | BigQuery offers on-demand pricing per TiB scanned (first 1 TiB per month free) or capacity pricing per slot-hour. BigQuery Omni has its own on-demand per TiB pricing for AWS regions. The page text shows $0.06 per slot-hour for Enterprise edition pay-as-you-go compute, with no region shown beside the rate (read 2026-11-10). Google's Spark service (Managed Service for Apache Spark, formerly Dataproc) bills serverless Spark per second in Data Compute Units with a 1-minute minimum, plus shuffle storage; Standard tier is for batch ETL, Premium tier uses Lightning Engine. |
| 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. | On BigQuery Omni, DML statements and CREATE TABLE are not supported, BigQuery ML statements are not supported, and only EXPORT DATA queries are allowed for destination tables, so it does not run write-heavy Spark batch ETL on S3. Standard and Enterprise Plus editions do not support Omni regions. BigQuery stored procedures for Apache Spark let you run PySpark or Scala/Java JAR code from SQL via CREATE PROCEDURE ... OPTIONS(engine = "SPARK", runtime_version = "2.2"), using a Cloud Storage file or inline code and a connection; this runs on Google Cloud, so code must be wrapped as procedures. |
| 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 managed tables run automatic storage optimization (adaptive file sizing, clustering, garbage collection), so compaction needs no job configuration on Google Cloud; storage optimization is a separate billed item. |
| 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'). | BigQuery Iceberg managed tables store data in buckets you own, support DML, streaming and Spark connectors, export Iceberg V2 snapshots for open engines, and do automatic compaction, clustering and garbage collection. BigLake tables let you query structured data in Cloud Storage, Amazon S3 and Blob Storage with access delegation and row and column security. |
| 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'. | BigQuery Omni lets BigQuery analytics run on data in Amazon S3 through BigLake tables, in AWS regions us-east-1, us-west-2, ap-northeast-2, ap-southeast-2, eu-west-1 and eu-central-1. |
| 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). | None found on 10 Nov 2026. |
| Compute Bill | DualBird on Amazon EMR (F2 instances): $49.50 | BigQuery (Enterprise edition slots): $19.20 |

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

- 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)
- Google BigQuery and BigLake: cloud.google.com/bigquery/docs/omni-introduction: https://cloud.google.com/bigquery/docs/omni-introduction (read 10 Nov 2026)
- Google BigQuery and BigLake: cloud.google.com/bigquery/docs/spark-procedures: https://cloud.google.com/bigquery/docs/spark-procedures (read 10 Nov 2026)
- Google BigQuery and BigLake: cloud.google.com/bigquery/docs/iceberg-tables: https://cloud.google.com/bigquery/docs/iceberg-tables (read 10 Nov 2026)
- Google BigQuery and BigLake: cloud.google.com/bigquery/docs/biglake-intro: https://cloud.google.com/bigquery/docs/biglake-intro (read 10 Nov 2026)
- Google BigQuery and BigLake: cloud.google.com/bigquery/pricing: https://cloud.google.com/bigquery/pricing (read 10 Nov 2026)
- Google BigQuery and BigLake: cloud.google.com/dataproc-serverless/pricing: https://cloud.google.com/dataproc-serverless/pricing (read 10 Nov 2026)

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