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

05110100:0006:0012:0018:0024:00vCPUProvisioned101 vCPUConsumed32 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 101 vCPU, set above a peak of 72 vCPU, costs 2425 vCPU-hours, while the workload actually consumes 778 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 15 101 86
01:00 15 101 86
02:00 15 101 86
03:00 15 101 86
04:00 15 101 86
05:00 15 101 86
06:00 15 101 87
07:00 20 101 81
08:00 34 101 67
09:00 47 101 54
10:00 57 101 44
11:00 65 101 36
12:00 70 101 31
13:00 70 101 31
14:00 67 101 34
15:00 60 101 41
16:00 50 101 51
17:00 37 101 64
18:00 24 101 77
19:00 15 101 86
20:00 15 101 86
21:00 15 101 86
22:00 15 101 86
23:00 15 101 86
How this is worked out
  • Demand is this estate's 32 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 72 vCPU plus the 40% headroom you picked, giving a ceiling of 101 vCPU. The headroom is an assumption rather than a published figure, so it's yours to argue with.
  • That peak is the 5 clusters' own peaks added up, because a provisioned estate buys each of them separately. Step 1's aggregate peak of 50 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 33.8% 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.

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