Dataproc Cluster Cost Calculator
Cost a Dataproc cluster including the per-vCPU premium, Spot secondary workers and disk, with idle time exposed.
About Dataproc Cluster Cost Calculator
Dataproc bills the underlying Compute Engine resources plus a premium on every vCPU, so the cluster shape drives both lines together. Secondary workers are the lever that matters: because they hold no HDFS data, running them on Spot capacity cuts the compute charge sharply while a job loss costs only the tasks in flight. Long-lived Dataproc clusters spend a large share of their hours idle, and the honest comparison is an ephemeral cluster created per job against a persistent one you keep warm for convenience. Confirm the Dataproc premium and Compute Engine rates for your region in the Google Cloud pricing calculator.
Formula
Dataproc Cluster Cost
cost = (on-demand vCPU + Spot vCPU × (1 − Spot discount)) × (vCPU price + GB per vCPU × GB price) × hours + total vCPU × Dataproc premium × hours + disk.
- Dataproc premium
- Management charge applied to every vCPU in the cluster, on top of Compute Engine
- secondary workers
- Spot workers that add compute without holding HDFS data
- idle share
- Cluster hours billed while no job is running
Worked example
With the default values below, Dataproc Cluster Cost Calculator returns Monthly Cost of $1,290.67. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Master nodesaccepts 1–3 nodes
- 1 nodes
- vCPUs per masteraccepts 1–96 vCPU
- 4 vCPU
- Primary workersaccepts 0–10,000 nodes
- 8 nodes
- vCPUs per workeraccepts 1–96 vCPU
- 8 vCPU
- Secondary (Spot) workersaccepts 0–10,000 nodes
- 10 nodes
- Compute Engine price per vCPU-houraccepts 0–10 USD/vCPU-hour
- 0.0316 USD/vCPU-hour
- Memory per vCPUaccepts 0.5–32 GB
- 4 GB
- Price per GB-houraccepts 0–10 USD/GB-hour
- 0.0042 USD/GB-hour
- Dataproc premium per vCPU-houraccepts 0–10 USD/vCPU-hour
- 0.01 USD/vCPU-hour
- Spot discount on secondary workersaccepts 0–91 %
- 70 %
- Cluster hours per monthaccepts 0–744 hours
- 200 hours
- Cluster hours with no job runningaccepts 0–100 %
- 25 %
- Persistent Disk per nodeaccepts 0–65,536 GB
- 500 GB
- Disk price per GB-monthaccepts 0–10 USD/GB-month
- 0.04 USD/GB-month
Results
- Monthly Cost
- $1,290.67
- Compute Engine Charge
- $890.56
- Dataproc Premium Charge
- $296.00
- Disk Charge
- $104.11
- vCPUs in the Cluster
- 148 vCPU
- Saved by Spot Secondary Workers
- $542.08
- Spent on Idle Cluster Time
- $322.67
- Cost per Cluster Hour
- $6.45
Step by step
- 1Values used
- 2Dataproc Cluster Cost
- 3Monthly Cost= 1,290.67
- 4Compute Engine Charge= 890.56
- 5Dataproc Premium Charge= 296.00
- 6Disk Charge= 104.11
- 7vCPUs in the Cluster= 148 vCPU
- 8Saved by Spot Secondary Workers= 542.08
Assumptions and limits
- The result is derived only from the 14 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax or compounding frequency into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
How is Dataproc Cluster Cost calculated?
cost = (on-demand vCPU + Spot vCPU × (1 − Spot discount)) × (vCPU price + GB per vCPU × GB price) × hours + total vCPU × Dataproc premium × hours + disk. Dataproc bills the underlying Compute Engine resources plus a premium on every vCPU, so the cluster shape drives both lines together. Secondary workers are the lever that matters: because they hold no HDFS data, running them on Spot capacity cuts the compute charge sharply while a job loss costs only the tasks in flight.
Why does Dataproc Cluster Cost matter?
Long-lived Dataproc clusters spend a large share of their hours idle, and the honest comparison is an ephemeral cluster created per job against a persistent one you keep warm for convenience. Confirm the Dataproc premium and Compute Engine rates for your region in the Google Cloud pricing calculator.
What values do I need to enter?
This calculator takes 14 inputs: Master nodes, vCPUs per master, Primary workers, vCPUs per worker, Secondary (Spot) workers, Compute Engine price per vCPU-hour, Memory per vCPU, Price per GB-hour, Dataproc premium per vCPU-hour, Spot discount on secondary workers, Cluster hours per month, Cluster hours with no job running, Persistent Disk per node, Disk price per GB-month. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Should the primary workers also be Spot?
No. Primary workers hold HDFS data, so losing one can force recomputation or leave the cluster under-replicated. Keep primaries on standard capacity for stability and put the elastic portion of the cluster into Spot secondary workers.