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

Estate summary

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

0612122400:0006:0012:0018:0024:00vCPUProvisioned1224 vCPUConsumed392 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 1224 vCPU, set above a peak of 874 vCPU, costs 29375 vCPU-hours, while the workload actually consumes 9418 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 177 1,224 1,047
01:00 178 1,224 1,046
02:00 178 1,224 1,046
03:00 177 1,224 1,047
04:00 179 1,224 1,045
05:00 181 1,224 1,043
06:00 176 1,224 1,048
07:00 243 1,224 981
08:00 410 1,224 814
09:00 568 1,224 656
10:00 696 1,224 528
11:00 784 1,224 440
12:00 846 1,224 378
13:00 850 1,224 374
14:00 809 1,224 415
15:00 729 1,224 495
16:00 607 1,224 617
17:00 451 1,224 773
18:00 289 1,224 935
19:00 177 1,224 1,047
20:00 180 1,224 1,044
21:00 178 1,224 1,046
22:00 178 1,224 1,046
23:00 179 1,224 1,045
How this is worked out
  • Demand is this estate's 392 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 874 vCPU plus the 40% headroom you picked, giving a ceiling of 1,224 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 489 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.3% 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.