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

Estate summary

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

0518103700:0006:0012:0018:0024:00vCPUProvisioned1037 vCPUConsumed332 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 1037 vCPU, set above a peak of 741 vCPU, costs 24884 vCPU-hours, while the workload actually consumes 7978 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 150 1,037 887
01:00 150 1,037 886
02:00 151 1,037 886
03:00 150 1,037 887
04:00 151 1,037 885
05:00 153 1,037 884
06:00 149 1,037 887
07:00 205 1,037 831
08:00 347 1,037 689
09:00 481 1,037 556
10:00 589 1,037 448
11:00 664 1,037 373
12:00 717 1,037 320
13:00 720 1,037 317
14:00 686 1,037 351
15:00 617 1,037 419
16:00 515 1,037 522
17:00 382 1,037 655
18:00 245 1,037 792
19:00 150 1,037 887
20:00 152 1,037 885
21:00 151 1,037 886
22:00 151 1,037 886
23:00 151 1,037 886
How this is worked out
  • Demand is this estate's 332 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 741 vCPU plus the 40% headroom you picked, giving a ceiling of 1,037 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 414 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.1% 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.