Home / Companies / Onehouse / Blog / Post Details
Content Deep Dive

Databricks DBU Cost: Prices, Calculation and Bill Drivers

Blog post from Onehouse

Post Details
Company
Date Published
Author
-
Word Count
3,096
Company Posts That Month
22
Language
English
Hacker News Points
-
Post removed?
No
Summary

Databricks Units (DBUs) are normalized processing units used to bill Databricks compute, with total costs determined by DBUs consumed, the rate for the selected compute type and service tier, and, for classic compute, separate cloud infrastructure charges. Premium AWS list prices cited range from $0.15 per DBU for classic jobs compute to $0.75 for serverless all-purpose compute, while Enterprise pricing is higher; rates also vary by cloud and region. Cluster size, runtime, idle capacity, Photon acceleration, and use of all-purpose rather than jobs clusters can substantially affect consumption, while serverless pricing bundles infrastructure but prevents customers from applying their own VM discounts. The text recommends analyzing usage through Databricks billing system tables, moving scheduled workloads to jobs clusters, reducing idle time and oversized capacity, evaluating Photon based on performance gains, and considering committed-use discounts and cloud capacity discounts. It also presents Quanton, a Spark execution engine from Onehouse that runs in a customer’s cloud environment and charges by data volume rather than DBUs, citing vendor-provided benchmark and cost comparisons that portray it as a potentially lower-cost option for certain scheduled Spark workloads, though results depend on workload characteristics, contracts, infrastructure pricing, and measured performance.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Serverless 24 1,363 319 106 +11%
Data Pipeline 3 397 159 72 +45%
Kubernetes 1 5,095 485 112 +17%
Real-time 1 4,128 1,085 233 -15%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.