Cockroach Labs Estate economics What idle nodes, provisioned bytes and peak-sized bills cost, worked out from your estate.
  1. Nodes 45 baseline
  2. Avg CPU utilization 15.0% idle hardware
  3. Storage provisioned 300 GB 50 GB of data
  4. Est. monthly saving 0%

Step 7 of 8 - Pricing

You pay for the area, not the rectangle

Provisioned capacity is a flat ceiling sized to the busiest fifteen minutes of the day, plus headroom for the peak you didn't forecast. The gap under that ceiling is hardware you rented and didn't use.

Run a day, 40% headroom Steady Business hours Batch spike

Provisioned capacity left unused

not started

Pick a day above. The ceiling is already drawn: it's sized to a peak of 120 vCPU plus 40%, and you pay for all of it whether the workload turns up or not. That's under the 360 vCPU the estate runs on today, which was bought a cluster at a time and works at 15.0%, not sized to this curve.

08416800:0006:0012:0018:0024:00vCPUProvisioned168 vCPUConsumed54 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 168 vCPU, set above a peak of 120 vCPU, costs 4042 vCPU-hours, while the workload actually consumes 1296 vCPU-hours: 68% of the provisioned capacity goes unused.
Provisioned
0 vCPU-hours
Consumed
0 vCPU-hours
Paid for, not used
0 vCPU-hours
Read this chart as a table
Mean demand per hour against provisioned capacity, in vCPU
HourDemandProvisionedUnused
00:00 24 168 144
01:00 24 168 144
02:00 24 168 144
03:00 24 168 144
04:00 25 168 144
05:00 25 168 144
06:00 24 168 144
07:00 33 168 135
08:00 56 168 112
09:00 78 168 90
10:00 96 168 73
11:00 108 168 61
12:00 116 168 52
13:00 117 168 51
14:00 111 168 57
15:00 100 168 68
16:00 84 168 85
17:00 62 168 106
18:00 40 168 129
19:00 24 168 144
20:00 25 168 144
21:00 24 168 144
22:00 25 168 144
23:00 25 168 144
How this is worked out
  • Demand is this estate's 54 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 120 vCPU plus the 40% headroom you picked, giving a ceiling of 168 vCPU. The headroom is an assumption rather than a published figure, so it's yours to argue with.
  • That peak is the 5 clusters' own peaks added up, because a provisioned estate buys each of them separately. Step 1's aggregate peak of 84 vCPU is the later, smaller question: what one pool needs once the workloads share it.
  • A ceiling that high averages 32.1% CPU across the day, which is the whole day's 67.9% of unused capacity counted the other way round. The pooled cluster on step 1 runs at 33.8% against a 37.5% setpoint. Neither number sets the other: this one is how far above the peak you buy, that one is what a controller is told to hold.
Where the storage number comes from

3 Raft copies at 50% utilization (3/0.5 = 6), on top of the block store's own internal replication.

50 GB of logical data becomes 300 GB provisioned , a factor of 6× before the cost model sees it.