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

Estate summary

  1. Nodes 346 baseline
  2. Avg CPU utilization 15.0% idle hardware
  3. Storage provisioned 3.0 TB 500 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 925 vCPU plus 40%, and you pay for all of it whether the workload turns up or not. That's under the 2,768 vCPU the estate runs on today, which was bought a cluster at a time and works at 15.0%, not sized to this curve.

0648129500:0006:0012:0018:0024:00vCPUProvisioned1295 vCPUConsumed415 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 1295 vCPU, set above a peak of 925 vCPU, costs 31082 vCPU-hours, while the workload actually consumes 9965 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 188 1,295 1,108
01:00 188 1,295 1,107
02:00 188 1,295 1,107
03:00 187 1,295 1,108
04:00 189 1,295 1,106
05:00 191 1,295 1,104
06:00 187 1,295 1,109
07:00 257 1,295 1,038
08:00 434 1,295 861
09:00 601 1,295 694
10:00 736 1,295 559
11:00 830 1,295 465
12:00 895 1,295 400
13:00 899 1,295 396
14:00 856 1,295 439
15:00 771 1,295 524
16:00 643 1,295 652
17:00 477 1,295 818
18:00 306 1,295 989
19:00 187 1,295 1,108
20:00 190 1,295 1,105
21:00 188 1,295 1,107
22:00 188 1,295 1,107
23:00 189 1,295 1,106
How this is worked out
  • Demand is this estate's 415 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 925 vCPU plus the 40% headroom you picked, giving a ceiling of 1,295 vCPU. The headroom is an assumption rather than a published figure, so it's yours to argue with.
  • That peak is the 50 clusters' own peaks added up, because a provisioned estate buys each of them separately. Step 1's aggregate peak of 487 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.5% 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.

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