# How the Lakehouse Compute Bill is calculated

Compute Bill method, read 10 Nov 2026

**The short answer.** The Lakehouse Compute Bill prices one reference job, ten r6i.4xlarge nodes for two hours in us-east-1, from prices read on 2026-11-10. Both groups are alphabetical, and mapped-group totals are read against their own assumptions, not against each other. A line with no published price shows No total.

## The reference workload

One nightly Spark batch job in AWS us-east-1: ten worker nodes of the r6i.4xlarge class (16 vCPU, 128 GiB), running for two hours, on-demand, reading and writing Apache Iceberg tables on S3. That is 20 node-hours, 160 vCPU and 1,280 GiB. The same job is used on every line.

## The price sources

Amazon prices come from the AWS Price List API for EC2 and EMR, published 2026-11-10: r6i.4xlarge is $1.008 per hour on EC2 and $0.252 per hour for the EMR price. Other prices come from each provider's own page or price API: the Snowflake Service Consumption Table dated 2026-11-09, Google's BigQuery page, the Azure Retail Prices API for Fabric, and the Starburst and Dremio pricing pages. Every unit price on the page names its source and read date.

## The arithmetic

Each line shows its formula in plain numbers: published unit price times the stated quantity, rounded to cents. Nothing is estimated and no performance number is derived. Platforms that do not bill by the instance (Snowflake, BigQuery, Fabric, Starburst, Dremio) need a mapping from the reference job to their unit, such as a warehouse size or a slot count. Those mappings are assumptions, and each line says so.

## What is excluded

- The driver or primary node, EBS volumes, S3 storage and requests, data transfer and public IPv4 charges.
- Support plans, enterprise discounts, Savings Plans, Reserved Instances and Spot.
- Engineering time to run the cluster, tune it and maintain Iceberg tables.
- Any price that is not published: those lines carry no total and say "None published on 2026-11-10".

## Why both groups are alphabetical

The bill has two groups. The first holds lines that price the same ten EC2 nodes: the open stack on EC2, EMR on EKS, EMR on EC2, EMR Serverless (which bills the same 160 vCPU and 1,280 GB as vCPU-hours and GB-hours, not as instances) and Databricks on AWS. The second holds lines whose own billing unit is mapped to the job by an assumption stated on the line: BigQuery, Microsoft Fabric, DualBird on EMR (ten f2.6xlarge nodes, a different instance type), Starburst, Snowflake, Dremio and Onehouse. Inside each group, lines are alphabetical by name, and a line with no total is shown in place. Totals in the first group share one set of nodes. Totals in the second group bill different units and engines, so each is read against its own stated assumption, not against the other lines. A different warehouse size, slot mapping or node count would move lines, and the platforms differ in what the price includes: some include a managed runtime, some are SQL engines rather than Spark, and Fabric runs on Azure. Read the cost note on each line before comparing two totals.

## How the calculator works

The reader changes the node count and the hours. The calculator multiplies those two numbers into the same formulas shown on each line. Prices stay as published; the calculator has no field for a price, a discount or a performance factor, and it does not change the mappings used for Snowflake, BigQuery, Fabric, Starburst or Dremio.

## How often prices are re-read

Prices on this page were read on 2026-11-10. The date beside each price is the date it was read. Cloud prices change without notice, so check the linked source before using a figure in a budget.

## Sources

- AWS Price List API, Amazon EMR, us-east-1 (published 2026-11-10): https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/ElasticMapReduce/current/us-east-1/index.json (read 10 Nov 2026)
- AWS Price List API, Amazon EC2, us-east-1 (published 2026-11-10): https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/us-east-1/index.json (read 10 Nov 2026)
- Amazon EMR pricing page: https://aws.amazon.com/emr/pricing/ (read 10 Nov 2026)
- Amazon EKS pricing page: https://aws.amazon.com/eks/pricing/ (read 10 Nov 2026)
- Snowflake Service Consumption Table, effective 2026-11-09: https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf (read 10 Nov 2026)
- Google BigQuery pricing page: https://cloud.google.com/bigquery/pricing (read 10 Nov 2026)
- Azure Retail Prices API, Microsoft Fabric, eastus: https://prices.azure.com/api/retail/prices?$filter=serviceName eq 'Microsoft Fabric' and armRegionName eq 'eastus' (read 10 Nov 2026)
- Microsoft Learn, Spark concurrency in Fabric: https://learn.microsoft.com/en-us/fabric/data-engineering/spark-job-concurrency-and-queueing (read 10 Nov 2026)
- Starburst Galaxy pricing details: https://www.starburst.io/pricing/pricing-details/ (read 10 Nov 2026)
- Dremio pricing page: https://www.dremio.com/pricing (read 10 Nov 2026)
- Dremio Cloud engines documentation: https://docs.dremio.com/dremio-cloud/admin/engines/ (read 10 Nov 2026)
- Onehouse usage and billing documentation: https://docs.onehouse.ai/product/project-settings/usage-and-billing (read 10 Nov 2026)
- Databricks AWS pricing page: https://www.databricks.com/product/aws-pricing (read 10 Nov 2026)
- Databricks pricing data file (AWS), loaded by its pricing calculator: https://www.databricks.com/en-pricing-assets/data/pricing/AWS.json (read 10 Nov 2026)
- Databricks Lakeflow Jobs pricing page: https://www.databricks.com/product/pricing/jobs (read 10 Nov 2026)
- Amazon EC2 F2 instances: https://aws.amazon.com/ec2/instance-types/f2/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalakehousecompare.com/compute-bill/method/
