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

046492800:0006:0012:0018:0024:00vCPUProvisioned928 vCPUConsumed298 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 928 vCPU, set above a peak of 663 vCPU, costs 22279 vCPU-hours, while the workload actually consumes 7142 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 134 928 794
01:00 135 928 794
02:00 135 928 794
03:00 134 928 794
04:00 136 928 793
05:00 137 928 791
06:00 134 928 795
07:00 184 928 744
08:00 311 928 617
09:00 431 928 498
10:00 528 928 401
11:00 595 928 334
12:00 642 928 286
13:00 644 928 284
14:00 614 928 314
15:00 553 928 375
16:00 461 928 468
17:00 342 928 586
18:00 219 928 709
19:00 134 928 794
20:00 136 928 792
21:00 135 928 793
22:00 135 928 793
23:00 135 928 793
How this is worked out
  • Demand is this estate's 298 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 663 vCPU plus the 40% headroom you picked, giving a ceiling of 928 vCPU. The headroom is an assumption rather than a published figure, so it's yours to argue with.
  • That peak is the 50 clusters' own peaks added up, because a provisioned estate buys each of them separately. Step 1's aggregate peak of 349 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.5% 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.

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