Dataproc Cluster Cost Calculator
Cost a Dataproc cluster including the per-vCPU premium, Spot secondary workers and disk, with idle time exposed.
Inputs
High-availability Dataproc runs three masters.
Secondary workers hold no HDFS data, so losing one only costs you the tasks in flight.
Monthly Cost
$1,290.67
Compute Engine Charge
$890.56
Dataproc Premium Charge
$296.00
Disk Charge
$104.11
vCPUs in the Cluster
148vCPU
Saved by Spot Secondary Workers
$542.08
Spent on Idle Cluster Time
$322.67
Cost per Cluster Hour
$6.45
Step by step
Values used
Master nodes = 1 nodes; vCPUs per master = 4 vCPU; Primary workers = 8 nodes; vCPUs per worker = 8 vCPU; Secondary (Spot) workers = 10 nodes; Compute Engine price per vCPU-hour = 0.0316 USD/vCPU-hour; Memory per vCPU = 4 GB; Price per GB-hour = 0.0042 USD/GB-hour; Dataproc premium per vCPU-hour = 0.0100 USD/vCPU-hour; Spot discount on secondary workers = 70 %; Cluster hours per month = 200 hours; Cluster hours with no job running = 25 %; Persistent Disk per node = 500 GB; Disk price per GB-month = 0.0400 USD/GB-month
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.
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
How it works
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
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.