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

012925800:0006:0012:0018:0024:00vCPUProvisioned258 vCPUConsumed180 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 258 vCPU, set above a peak of 184 vCPU, costs 6194 vCPU-hours, while the workload actually consumes 4320 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 179 258 79
01:00 182 258 77
02:00 179 258 79
03:00 181 258 77
04:00 178 258 80
05:00 180 258 78
06:00 182 258 76
07:00 178 258 80
08:00 179 258 79
09:00 180 258 78
10:00 180 258 78
11:00 178 258 80
12:00 182 258 76
13:00 180 258 79
14:00 182 258 76
15:00 179 258 79
16:00 181 258 78
17:00 179 258 79
18:00 181 258 77
19:00 180 258 78
20:00 181 258 77
21:00 179 258 79
22:00 181 258 77
23:00 178 258 80
How this is worked out
  • Demand is this estate's 180 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 184 vCPU plus the 40% headroom you picked, giving a ceiling of 258 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 181 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 36.9% 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.