Cockroach Labs Estate economics What idle nodes, provisioned bytes and peak-sized bills cost, worked out from your estate.
  1. Nodes 67 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 179 vCPU plus 40%, and you pay for all of it whether the workload turns up or not. That's under the 536 vCPU the estate runs on today, which was bought a cluster at a time and works at 15.0%, not sized to this curve.

012525100:0006:0012:0018:0024:00vCPUProvisioned251 vCPUConsumed80 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 251 vCPU, set above a peak of 179 vCPU, costs 6019 vCPU-hours, while the workload actually consumes 1930 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 36 251 214
01:00 36 251 214
02:00 36 251 214
03:00 36 251 215
04:00 37 251 214
05:00 37 251 214
06:00 36 251 215
07:00 50 251 201
08:00 84 251 167
09:00 116 251 134
10:00 143 251 108
11:00 161 251 90
12:00 173 251 77
13:00 174 251 77
14:00 166 251 85
15:00 149 251 101
16:00 124 251 126
17:00 92 251 158
18:00 59 251 192
19:00 36 251 215
20:00 37 251 214
21:00 36 251 214
22:00 36 251 214
23:00 37 251 214
How this is worked out
  • Demand is this estate's 80 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 179 vCPU plus the 40% headroom you picked, giving a ceiling of 251 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 125 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 34.7% 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.