Skip to content
Lakehouse Compare

Side by side, read 10 Nov 2026

Onehouse and Open stack on EMR and EKS: the published facts in the same rows

Onehouse profileOpen stack on EMR and EKS profile

The same rows for both

Alphabetical order. Vendor statements are the vendor's own. Read 10 Nov 2026.
RowOnehouseOpen stack on EMR and EKS
KindManaged lakehouse in your cloud accountSelf-run Spark with open table formats
Does wellPer 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).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.
LimitedPer 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.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 resultsOnehouse 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.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 resultsOnehouse 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.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 migrationOnehouse 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.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 upkeepEach 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.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 formatsQuanton 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.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 runsOnehouse 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.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 areOnehouse 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.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 BillOnehouse (Quanton, bring-your-own-cloud): no total (see the Compute Bill for why)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

  1. Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/jobs/emr-migration, read 10 Nov 2026
  2. Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/announcing-spark-and-sql-on-the-onehouse-compute-runtim, read 10 Nov 2026
  3. Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/project-settings/usage-and-billing, read 10 Nov 2026
  4. Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/jobs, read 10 Nov 2026
  5. Onehouse (Onehouse Compute Runtime with the Quanton engine): xtable.apache.org, read 10 Nov 2026
  6. Onehouse (Onehouse Compute Runtime with the Quanton engine): docs.onehouse.ai/product/compute/create-cluster, read 10 Nov 2026
  7. Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/apache-iceberg-on-quanton-3x-faster-apache-spark-worklo, read 10 Nov 2026
  8. 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
  9. Onehouse (Onehouse Compute Runtime with the Quanton engine): onehouse.ai/blog/emr-migration-to-quanton-spark-udf-jobs, read 10 Nov 2026
  10. Onehouse (Onehouse Compute Runtime with the Quanton engine): api.github.com/repos/onehouseinc/lake-loader, read 10 Nov 2026
  11. Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: aws.amazon.com/emr/pricing, read 10 Nov 2026
  12. 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
  13. 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
  14. 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
  15. Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: iceberg.apache.org/docs/latest/maintenance, read 10 Nov 2026
  16. Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: hudi.apache.org/docs/compaction, read 10 Nov 2026
  17. Open stack: Spark on EMR or EKS with Iceberg, Delta or Hudi: docs.delta.io/latest/optimizations-oss.html, read 10 Nov 2026
  18. 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
  19. 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.