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

Estate summary

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

061100:0006:0012:0018:0024:00vCPUProvisioned11 vCPUConsumed4 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 11 vCPU, set above a peak of 8 vCPU, costs 269 vCPU-hours, while the workload actually consumes 86 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 2 11 10
01:00 2 11 10
02:00 2 11 10
03:00 2 11 10
04:00 2 11 10
05:00 2 11 10
06:00 2 11 10
07:00 2 11 9
08:00 4 11 7
09:00 5 11 6
10:00 6 11 5
11:00 7 11 4
12:00 8 11 3
13:00 8 11 3
14:00 7 11 4
15:00 7 11 5
16:00 6 11 6
17:00 4 11 7
18:00 3 11 9
19:00 2 11 10
20:00 2 11 10
21:00 2 11 10
22:00 2 11 10
23:00 2 11 10
How this is worked out
  • Demand is this estate's 4 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 8 vCPU plus the 40% headroom you picked, giving a ceiling of 11 vCPU. The headroom is an assumption rather than a published figure, so it's yours to argue with.
  • 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 15.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.

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