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

013126200:0006:0012:0018:0024:00vCPUProvisioned262 vCPUConsumed84 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 262 vCPU, set above a peak of 187 vCPU, costs 6288 vCPU-hours, while the workload actually consumes 2016 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 38 262 224
01:00 38 262 224
02:00 38 262 224
03:00 38 262 224
04:00 38 262 224
05:00 39 262 223
06:00 38 262 224
07:00 52 262 210
08:00 88 262 174
09:00 122 262 140
10:00 149 262 113
11:00 168 262 94
12:00 181 262 81
13:00 182 262 80
14:00 173 262 89
15:00 156 262 106
16:00 130 262 132
17:00 97 262 166
18:00 62 262 200
19:00 38 262 224
20:00 38 262 224
21:00 38 262 224
22:00 38 262 224
23:00 38 262 224
How this is worked out
  • Demand is this estate's 84 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 187 vCPU plus the 40% headroom you picked, giving a ceiling of 262 vCPU. The headroom is an assumption rather than a published figure, so it's yours to argue with.
  • That peak is the 10 clusters' own peaks added up, because a provisioned estate buys each of them separately. Step 1's aggregate peak of 117 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.0% 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.

100 GB of logical data becomes 600 GB provisioned , a factor of 6× before the cost model sees it.