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

01404280700:0006:0012:0018:0024:00vCPUProvisioned2807 vCPUConsumed900 vCPU avgProvisioned capacity versus consumption over 24 hoursOver 24 hours, a ceiling of 2807 vCPU, set above a peak of 2005 vCPU, costs 67375 vCPU-hours, while the workload actually consumes 21600 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 407 2,807 2,401
01:00 407 2,807 2,400
02:00 408 2,807 2,400
03:00 405 2,807 2,402
04:00 410 2,807 2,397
05:00 414 2,807 2,393
06:00 404 2,807 2,403
07:00 556 2,807 2,251
08:00 940 2,807 1,867
09:00 1,302 2,807 1,505
10:00 1,596 2,807 1,212
11:00 1,799 2,807 1,009
12:00 1,941 2,807 866
13:00 1,949 2,807 858
14:00 1,856 2,807 951
15:00 1,672 2,807 1,136
16:00 1,393 2,807 1,414
17:00 1,034 2,807 1,773
18:00 663 2,807 2,145
19:00 406 2,807 2,401
20:00 412 2,807 2,395
21:00 408 2,807 2,399
22:00 408 2,807 2,399
23:00 410 2,807 2,398
How this is worked out
  • Demand is this estate's 900 vCPU mean, shaped by the preset you picked, which also drives step 1.
  • Capacity is sized at the day's peak of 2,005 vCPU plus the 40% headroom you picked, giving a ceiling of 2,807 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 1,056 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.6% 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.