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

042585000:0006:0012:0018:0024:00vCPUProvisioned850 vCPUConsumed272 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 850 vCPU, set above a peak of 607 vCPU, costs 20392 vCPU-hours, while the workload actually consumes 6538 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 123 850 727
01:00 123 850 726
02:00 123 850 726
03:00 123 850 727
04:00 124 850 726
05:00 125 850 724
06:00 122 850 727
07:00 168 850 681
08:00 285 850 565
09:00 394 850 456
10:00 483 850 367
11:00 544 850 305
12:00 587 850 262
13:00 590 850 260
14:00 562 850 288
15:00 506 850 344
16:00 422 850 428
17:00 313 850 537
18:00 201 850 649
19:00 123 850 727
20:00 125 850 725
21:00 123 850 726
22:00 124 850 726
23:00 124 850 726
How this is worked out
  • Demand is this estate's 272 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 607 vCPU plus the 40% headroom you picked, giving a ceiling of 850 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 339 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 36.2% 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.