Cockroach Labs Estate economics What idle nodes, provisioned bytes and peak-sized bills cost, worked out from your estate.
  1. Nodes 3 baseline
  2. Avg CPU utilization 15.0% idle hardware
  3. Storage provisioned 6.0 TB 1.0 TB of data
  4. Est. monthly saving 0%

Step 1 of 8 - Virtualization

You're running an estate, not a cluster

Every cluster below was sized for its own peak, so every one of them idles.

Deployment model
Separate clusters One Private Host Cluster
1 standalone cluster, 3 nodes in totalcluster-0115% CPU3 nodesEstate before consolidation1 separate cluster of around 3 nodes each, 3 nodes in total, averaging 15.0% CPU utilization.
15%Average CPUAverage CPU CPU utilization15.0% of provisioned CPU is in use.

3 nodes running 4 vCPU of actual work.

The arithmetic, in full
StepWorkingResult
Provisioned today1 cluster of 3 nodes x 8 vCPU24 vCPU
Mean demand24 vCPU x 15.0% estate average utilization4 vCPU
Aggregate peak3.6 vCPU x (1 + (2.23 - 1) / sqrt(1)), a pooled peak-to-mean of 2.2288 vCPU
Consolidated, sized once for the peakmax(3, ceil(8.0 vCPU / (8 vCPU x 37.5% target))) = max(3, ceil(2.67)); the mean sits well under that peak3 nodes, averaging 15.0%
Auto-scaled through the daythe pool follows the pooled curve in whole nodes, 30 minutes behind it, holding its size for 2 hours before shrinking3 nodes on average, at 15.0% CPU
Utilization across the day6.6% to 33.4% against a 37.5% setpoint: the pool sits on its 3-node floor all day, so this is the workload's own range rather than the controller's6.6%-33.4%

Assumptions

  • 8 vCPU per node. Standalone clusters are drawn around 3 nodes, snapped to an odd number for quorum and held between 3 and 15; this estate is one cluster of 3.
  • Each standalone cluster's CPU is a draw from a normal distribution centred on 15.0% and held between 0% and 100%; with one cluster there's nothing to average against, so it sits on 15.0% exactly. The published band is 10-15% today against a 30-45% auto-scaled target, and this Private Host Cluster is set to 37.5%.
  • The Private Host Cluster floors at 3 nodes and must reach 3 at peak.
  • The auto-scaler sizes for what it saw 30 minutes ago and waits 2 hours before shrinking, so the pool averages 15.0% rather than sitting on its 37.5% setpoint.
  • Workloads are independent; consolidation moves where work runs, not how much there is.
What a virtual cluster gives an app team

Its own connection string, databases, schemas, users, roles and backups, and no visibility into the Private Host Cluster or any other virtual cluster.