Skip to content
Lakehouse Compare

Side by side, read 10 Nov 2026

Google BigQuery and BigLake and Onehouse: the published facts in the same rows

Google BigQuery and BigLake profileOnehouse profile

The same rows for both

Alphabetical order. Vendor statements are the vendor's own. Read 10 Nov 2026.
RowGoogle BigQuery and BigLakeOnehouse
KindServerless Google Cloud data warehouseManaged lakehouse in your cloud account
Does wellPer 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).Per Onehouse documentation, its jobs are fully compatible with Apache Spark and EMR code can be reused unless it uses AWS-specific features (read 2026-11-10). Onehouse published the setup for its 10 TB TPC-DS and 1 TB LakeLoader comparison against EMR 7.12, and open-sourced LakeLoader under Apache-2.0 (read 2026-11-10).
LimitedPer 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.Per Onehouse documentation, billing is in OCUs on a bring-your-own-cloud model, and no dollar rate per OCU was found on 2026-11-10. Onehouse's results against EMR 7.12 are its own and shown as charts; a confirmation by another party: none found on 2026-11-10.
Published speed resultsGoogle 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.Onehouse benchmarked Quanton against open-source Spark on Iceberg: TPC-DS up to about 3.1x, TPCx-BB 2x, TPC-DI (1 TB) 2x with 3-4x on MERGE INTO, and LakeLoader 4.1x for writes. The baseline is open-source Spark, not EMR. Onehouse reran its benchmarks against EMR 7.12 after AWS announced it: it reports EMR improved 32% over earlier versions and that Onehouse 'still comes out with a 2.5x better price/performance advantage'. Setup: 10 TB TPC-DS for read/transform, 1 TB LakeLoader merges for load, latest general-purpose Graviton instances. Results are shown as charts; Onehouse also reports Hudi and Delta query performance on EMR 7.12 was very similar to Iceberg. A B2B SaaS customer (unnamed) ran its UDF-heavy pipeline on EMR and on Quanton in its own AWS account on m8gd nodes. Quanton was faster at p50, p97 and p99 tenant sizes; on the largest tenant (21 billion rows) EMR filled local disks on 180 nodes and was aborted after 3.7 hours, and finished on 300 nodes. The write-up is published by Onehouse.
Published prices and cost resultsBigQuery 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.Onehouse bills in Onehouse Compute Units (OCU) on a bring-your-own-cloud model: 1 OCU is a 4-core instance for 1 hour in your account, plus support costs; no separate volume or storage fee, and the customer pays its own AWS or GCP infrastructure bill. The docs page does not state a dollar rate per OCU. Vendor claims at the Quanton launch: 2-3x better price-performance for ETL, and a guaranteed greater-than-50% cost reduction for existing Hudi users moving Spark jobs from AWS EMR or open-source Spark. These are guarantees stated by the vendor, not results from an independent party.
Code changes and migrationOn 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.Onehouse docs say its Jobs are fully compatible with Apache Spark and that EMR code can be reused unless it uses AWS-specific features. Migration work listed: map EMR steps to Onehouse Jobs created through its API or Airflow operators (CREATE CLUSTER, CREATE JOB, RUN JOB, DELETE CLUSTER), and configure Glue catalog sync or contact support to make Glue the primary catalog. At the May 20, 2025 launch Onehouse said users can run existing Spark and SQL jobs on new cluster types and that existing Hudi/Spark jobs can be pointed at Onehouse 'with no code changes'. The Quanton Kubernetes Operator is described as a 'drop-in replacement' for an existing Spark Kubernetes operator.
Tuning and table upkeepIceberg 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.Each cluster needs min and max OCU limits. Docs warn that if usage reaches Max OCU the cluster stops scaling up, which can delay processing; Min OCU keeps a cluster warm. The Onehouse docs pages read give no per-job Spark tuning list; Onehouse claims automatic scaling and automated async table services.
Spark versions and table formatsBigQuery 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.Quanton runs Spark and SQL jobs that read and write Hudi, Iceberg and Delta Lake. Docs: Iceberg 1.10.0 is installed automatically when a job uses an Iceberg REST Catalog (AWS Glue and Snowflake Open Catalog are documented); for Delta Lake the user installs Delta Spark as a dependency in the JAR or Python job. In the Nov 12, 2025 Iceberg post Onehouse said Delta acceleration is 'up next'. Apache XTable (formerly OneTable) translates table metadata between Hudi, Delta Lake and Iceberg without being a new format. It is incubating at the Apache Software Foundation; Onehouse says it created Hudi and XTable.
Where it runsBigQuery 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.Onehouse runs EC2 or Google Compute Engine instances inside the customer's AWS or GCP account (Azure not listed in the billing docs). Standard instance types map to Graviton m8g sizes on AWS (oh-general-4 = m8g.xlarge, oh-general-8 = m8g.2xlarge, oh-general-16 = m8g.4xlarge). A project is scoped to one region and account; adding a region needs a support ticket.
How open its benchmarks areNone found on 10 Nov 2026.Onehouse open-sourced LakeLoader, a tool that generates incremental update/insert loads for benchmarking write performance. The repository is Apache-2.0 licensed, last pushed 2026-10-30. The Quanton engine itself and the full Iceberg benchmark configurations were not found as a repository in the pages read.
Compute BillBigQuery (Enterprise edition slots): $19.20Onehouse (Quanton, bring-your-own-cloud): no total (see the Compute Bill for why)

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

  1. Google BigQuery and BigLake: cloud.google.com/bigquery/docs/omni-introduction, read 10 Nov 2026
  2. Google BigQuery and BigLake: cloud.google.com/bigquery/docs/spark-procedures, read 10 Nov 2026
  3. Google BigQuery and BigLake: cloud.google.com/bigquery/docs/iceberg-tables, read 10 Nov 2026
  4. Google BigQuery and BigLake: cloud.google.com/bigquery/docs/biglake-intro, read 10 Nov 2026
  5. Google BigQuery and BigLake: cloud.google.com/bigquery/pricing, read 10 Nov 2026
  6. Google BigQuery and BigLake: cloud.google.com/dataproc-serverless/pricing, read 10 Nov 2026
  7. Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/jobs/emr-migration, read 10 Nov 2026
  8. Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/announcing-spark-and-sql-on-the-onehouse-compute-runtim, read 10 Nov 2026
  9. Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/project-settings/usage-and-billing, read 10 Nov 2026
  10. Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/jobs, read 10 Nov 2026
  11. Onehouse (Onehouse Compute Runtime with the Quanton engine): xtable.apache.org, read 10 Nov 2026
  12. Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/compute/create-cluster, read 10 Nov 2026
  13. Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/apache-iceberg-on-quanton-3x-faster-apache-spark-worklo, read 10 Nov 2026
  14. Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/onehouse-quanton-vs-the-latest-aws-emr-for-apache-spark, read 10 Nov 2026
  15. Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/emr-migration-to-quanton-spark-udf-jobs, read 10 Nov 2026
  16. Onehouse (Onehouse Compute Runtime with the Quanton engine): api.github.com/repos/onehouseinc/lake-loader, read 10 Nov 2026

Last reviewed 10 Nov 2026.