Cockroach Labs Estate economics What idle nodes, provisioned bytes and peak-sized bills cost, worked out from your estate.
  1. Nodes 5 baseline
  2. Avg CPU utilization 15.0% idle hardware
  3. Storage provisioned 60 GB plus 10 GB in S3
  4. Est. monthly saving 11% $1,000/m becomes $890/m

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

091900:0006:0012:0018:0024:00vCPUProvisioned19 vCPUConsumed6 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 19 vCPU, set above a peak of 13 vCPU, costs 449 vCPU-hours, while the workload actually consumes 144 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 3 19 16
01:00 3 19 16
02:00 3 19 16
03:00 3 19 16
04:00 3 19 16
05:00 3 19 16
06:00 3 19 16
07:00 4 19 15
08:00 6 19 12
09:00 9 19 10
10:00 11 19 8
11:00 12 19 7
12:00 13 19 6
13:00 13 19 6
14:00 12 19 6
15:00 11 19 8
16:00 9 19 9
17:00 7 19 12
18:00 4 19 14
19:00 3 19 16
20:00 3 19 16
21:00 3 19 16
22:00 3 19 16
23:00 3 19 16
How this is worked out
  • Demand is this estate's 6 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 13 vCPU plus the 40% headroom you picked, giving a ceiling of 19 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 18.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 shared copies at 50% utilization (3/0.5 = 6), plus 1 copy in S3. Consolidate to lift utilization to 75%. Billed as used: the 40 GB on disk, not the 70 GB of capacity holding them.

10 GB of logical data becomes 60 GB provisioned plus 10 GB in object storage, a factor of 7× before the cost model sees it.

The console quotes no storage estimate for Plenum - the bytes aren't known until they're held - so this is the demo's model of the meter, not a figure you can read back off a price page.