YALineo
EN
Install

Estimate a Databricks workload's cost before you run it

The cost of a Databricks workload can be prepared before it runs: DBUs at a price per SKU, plus the cloud machines when the compute is not serverless. Here is what it is made of, how to estimate it and then check it, and what YALineo does.

Updated on 6 November 2026 · Abdouramane Youssouf

What a workload's cost is made of

A Databricks workload (job, pipeline, SQL warehouse, all-purpose cluster) consumes DBUs. Databricks defines the DBU as a normalized unit of processing power. Billing is per second.

Part of the costBilled byVaries with
DBUs consumedDatabricks (on Azure, Microsoft)Type and number of machines, Photon, warehouse size, hours
Price of a DBUDatabricks (on Azure, Microsoft)Product (its SKU), cloud, region, plan, discounts
Classic compute machinesThe cloud providerType, number, hours, payment: on demand, spot or reserved
Disks, storage, networkThe cloud provider; storage managed by Databricks is counted in DSUsServices chosen, cloud, region

Each product has its own price per DBU: Jobs Compute, All-Purpose Compute, SQL Pro Compute or Serverless SQL on Azure. According to Databricks, a non-interactive workload costs significantly less on job compute than on all-purpose compute.

On serverless, the DBU price includes the virtual machines. On classic compute, the machines, their disks and the network come on top of the DBUs. Azure also bills managed disks, blob storage and public IP addresses.

The formula

DBUs per hour = DBU(driver) + workers × DBU(worker)      classic compute
              = DBU(size) × clusters                     SQL warehouse
DBU cost      = DBUs per hour × hours × price of a DBU × (1 − DBU discount)
Machine cost  = (price(driver) + workers × price(worker)) × hours × (1 − machine discount)
Total         = DBU cost + machine cost

DBU(type), the DBUs per hour of an instance type, is published by each cloud; Photon raises it. On Azure, a Pro or Classic warehouse has the same DBUs per hour as serverless, plus the price of its machines. For a serverless job, measure the DBUs of one run on a test.

A worked example

A serverless SQL warehouse of size Small. Only its DBUs per hour come from an official page; the rest is an assumption.

InputValueOrigin
DBUs per hour, size Small12Microsoft Learn, Serverless DBU consumption by SKU
Hours on per month8 h × 22 days = 176 hAssumption
Price of a DBU$1.00Made-up price, round so the arithmetic is easy to follow
DBU discount10%Assumption
Machines$0Included in the serverless DBU price

DBUs per month: 12 × 176 = 2,112. Cost: 2,112 × $1.00 × (1 − 0.10) = $1,900.80 per month.

Estimate before you create the workload

Hours

For a job, multiply the runs per month by the duration of one run, measured on a test. A warehouse or a cluster is paid for as long as it is on, idle time included. According to Microsoft, a SQL warehouse's auto stop comes by default after 10 minutes on serverless and 45 minutes on Pro and Classic. Databricks adds that a Pro or Classic warehouse takes minutes to start, and a serverless one a few seconds.

Size, autoscaling and Photon

With autoscaling, a cluster's workers or a warehouse's clusters vary between a minimum and a maximum. Price an average, then the minimum and the maximum. Photon raises the DBUs per hour: the cost goes down only if the run gets faster by a factor larger than the rise in the price of an hour. Databricks advises testing it on regular jobs.

Spot, reservations and discounts

The official calculators

Check the estimate after launch

Put a tag on the workload before you launch it. According to Databricks, a tag only applies to future usage, and it also reaches the cloud resources. Then compare the estimate with the measured usage:

SELECT u.usage_date,
       SUM(u.usage_quantity) AS dbu,
       SUM(u.usage_quantity * p.pricing.effective_list.default) AS list_price_cost
FROM system.billing.usage AS u
JOIN system.billing.list_prices AS p
  ON u.cloud = p.cloud
 AND u.sku_name = p.sku_name
 AND u.usage_unit = p.usage_unit
 AND u.usage_end_time >= p.price_start_time
 AND (p.price_end_time IS NULL OR u.usage_end_time < p.price_end_time)
WHERE u.custom_tags['workload'] = 'finance-dashboards'
  AND u.usage_date >= date_sub(current_date(), 30)
GROUP BY ALL

Without a tag, filter on usage_metadata.job_id (empty for a job launched on an all-purpose cluster) or usage_metadata.warehouse_id. Rows typically arrive within 12 hours. A DBU gap points to the assumption to revisit: hours, size or Photon. For classic compute, node hours are in system.compute.node_timeline, without serverless or SQL warehouses. The machine cost is in the cloud bill.

What an estimate does not tell

What YALineo does

YALineo's Calculator prices a job, a pipeline, a SQL warehouse or a cluster on Azure, AWS or GCP before you create it: DBUs, machines, total per month and per year. It works without a workspace, with the public prices of a dated snapshot bundled in the extension. Each figure says whether it is public, measured or entered (prices and their origin).

Fictional worked cases help you learn the tool. The formulas are in the Calculator method.

Frequently asked questions

Does serverless cost more than classic compute?

Its price per DBU includes the machines; the classic one does not. Compare the total of both for the same workload and the same hours.

Where do I find my contract's price of a DBU?

system.billing.list_prices gives the list price of each SKU of your account, promotions included in effective_list. Your contract discount is not in it. On Azure, the pricing calculator shows your offer's prices once you sign in.

Do I need a workspace for YALineo's Calculator?

No. A workspace lets you start from your measured workloads and read your account's prices.

Sources

Documentation read on 6 November 2026.