Cockroach Labs Estate economics What idle nodes, provisioned bytes and peak-sized bills cost, worked out from your estate.
  1. Nodes 30 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 152 vCPU plus 40%, and you pay for all of it whether the workload turns up or not. That's under the 240 vCPU the estate runs on today, which was bought a cluster at a time and works at 15.0%, not sized to this curve.

010721300:0006:0012:0018:0024:00vCPUProvisioned213 vCPUConsumed36 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 213 vCPU, set above a peak of 152 vCPU, costs 5124 vCPU-hours, while the workload actually consumes 864 vCPU-hours: 83% 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 18 213 195
01:00 61 213 153
02:00 93 213 121
03:00 19 213 194
04:00 18 213 195
05:00 19 213 195
06:00 19 213 195
07:00 22 213 191
08:00 33 213 181
09:00 41 213 172
10:00 49 213 164
11:00 55 213 159
12:00 57 213 156
13:00 58 213 156
14:00 56 213 158
15:00 50 213 163
16:00 44 213 170
17:00 35 213 179
18:00 25 213 188
19:00 18 213 195
20:00 19 213 195
21:00 18 213 195
22:00 19 213 195
23:00 19 213 195
How this is worked out
  • Demand is this estate's 36 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 152 vCPU plus the 40% headroom you picked, giving a ceiling of 213 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 73 vCPU is the later, smaller question: what one pool needs once the workloads share it.
  • A ceiling that high averages 16.9% CPU across the day, which is the whole day's 83.1% of unused capacity counted the other way round. The pooled cluster on step 1 runs at 32.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.

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