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

026753400:0006:0012:0018:0024:00vCPUProvisioned534 vCPUConsumed90 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 534 vCPU, set above a peak of 381 vCPU, costs 12809 vCPU-hours, while the workload actually consumes 2160 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 46 534 488
01:00 152 534 382
02:00 231 534 302
03:00 48 534 486
04:00 46 534 488
05:00 47 534 487
06:00 46 534 487
07:00 56 534 478
08:00 82 534 451
09:00 103 534 430
10:00 124 534 410
11:00 136 534 397
12:00 144 534 390
13:00 145 534 389
14:00 139 534 395
15:00 126 534 408
16:00 109 534 425
17:00 87 534 446
18:00 63 534 471
19:00 46 534 488
20:00 46 534 487
21:00 46 534 488
22:00 46 534 487
23:00 47 534 487
How this is worked out
  • Demand is this estate's 90 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 381 vCPU plus the 40% headroom you picked, giving a ceiling of 534 vCPU. The headroom is an assumption rather than a published figure, so it's yours to argue with.
  • That peak is the 25 clusters' own peaks added up, because a provisioned estate buys each of them separately. Step 1's aggregate peak of 148 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 34.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.

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