Cockroach Labs Estate economics What idle nodes, provisioned bytes and peak-sized bills cost, worked out from your estate.

Estate summary

  1. Nodes 127 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 340 vCPU plus 40%, and you pay for all of it whether the workload turns up or not. That's under the 1,016 vCPU the estate runs on today, which was bought a cluster at a time and works at 15.0%, not sized to this curve.

023847500:0006:0012:0018:0024:00vCPUProvisioned475 vCPUConsumed152 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 475 vCPU, set above a peak of 340 vCPU, costs 11409 vCPU-hours, while the workload actually consumes 3658 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 69 475 407
01:00 69 475 406
02:00 69 475 406
03:00 69 475 407
04:00 69 475 406
05:00 70 475 405
06:00 68 475 407
07:00 94 475 381
08:00 159 475 316
09:00 221 475 255
10:00 270 475 205
11:00 305 475 171
12:00 329 475 147
13:00 330 475 145
14:00 314 475 161
15:00 283 475 192
16:00 236 475 239
17:00 175 475 300
18:00 112 475 363
19:00 69 475 407
20:00 70 475 406
21:00 69 475 406
22:00 69 475 406
23:00 69 475 406
How this is worked out
  • Demand is this estate's 152 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 340 vCPU plus the 40% headroom you picked, giving a ceiling of 475 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 190 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 35.9% 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.