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

025851600:0006:0012:0018:0024:00vCPUProvisioned516 vCPUConsumed360 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 516 vCPU, set above a peak of 369 vCPU, costs 12387 vCPU-hours, while the workload actually consumes 8640 vCPU-hours: 30% 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 358 516 158
01:00 363 516 153
02:00 358 516 158
03:00 362 516 154
04:00 357 516 159
05:00 361 516 155
06:00 364 516 152
07:00 356 516 160
08:00 359 516 157
09:00 361 516 156
10:00 361 516 155
11:00 356 516 161
12:00 364 516 153
13:00 359 516 157
14:00 364 516 152
15:00 358 516 159
16:00 361 516 155
17:00 359 516 157
18:00 361 516 155
19:00 360 516 156
20:00 363 516 153
21:00 358 516 158
22:00 363 516 154
23:00 357 516 159
How this is worked out
  • Demand is this estate's 360 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 369 vCPU plus the 40% headroom you picked, giving a ceiling of 516 vCPU. The headroom is an assumption rather than a published figure, so it's yours to argue with.
  • That peak is the 100 clusters' own peaks added up, because a provisioned estate buys each of them separately. Step 1's aggregate peak of 361 vCPU is the later, smaller question: what one pool needs once the workloads share it.
  • A ceiling that high averages 69.7% CPU across the day, which is the whole day's 30.3% of unused capacity counted the other way round. The pooled cluster on step 1 runs at 37.2% 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.

1.0 TB of logical data becomes 6.0 TB provisioned , a factor of 6× before the cost model sees it.