Cockroach Labs Estate economics What idle nodes, provisioned bytes and peak-sized bills cost, worked out from your estate.
  1. Nodes 75 baseline
  2. Avg CPU utilization 15.0% idle hardware
  3. Storage provisioned 1.5 TB 250 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 201 vCPU plus 40%, and you pay for all of it whether the workload turns up or not. That's under the 600 vCPU the estate runs on today, which was bought a cluster at a time and works at 15.0%, not sized to this curve.

014028100:0006:0012:0018:0024:00vCPUProvisioned281 vCPUConsumed90 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 281 vCPU, set above a peak of 201 vCPU, costs 6737 vCPU-hours, while the workload actually consumes 2160 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 41 281 240
01:00 41 281 240
02:00 41 281 240
03:00 41 281 240
04:00 41 281 240
05:00 41 281 239
06:00 40 281 240
07:00 56 281 225
08:00 94 281 187
09:00 130 281 151
10:00 160 281 121
11:00 180 281 101
12:00 194 281 87
13:00 195 281 86
14:00 186 281 95
15:00 167 281 114
16:00 139 281 141
17:00 103 281 177
18:00 66 281 214
19:00 41 281 240
20:00 41 281 240
21:00 41 281 240
22:00 41 281 240
23:00 41 281 240
How this is worked out
  • Demand is this estate's 90 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 201 vCPU plus the 40% headroom you picked, giving a ceiling of 281 vCPU. The headroom is an assumption rather than a published figure, so it's yours to argue with.
  • That peak is the 25 clusters' own peaks added up, because a provisioned estate buys each of them separately. Step 1's aggregate peak of 112 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 36.3% 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.

250 GB of logical data becomes 1.5 TB provisioned , a factor of 6× before the cost model sees it.