Cockroach Labs Estate economics What idle nodes, provisioned bytes and peak-sized bills cost, worked out from your estate.
  1. Nodes 346 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 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
50 standalone clusters, 346 nodes in totalcluster-0110% CPU9 nodescluster-025% CPU7 nodescluster-0322% CPU7 nodescluster-0417% CPU5 nodescluster-059% CPU7 nodescluster-0614% CPU9 nodescluster-0710% CPU5 nodescluster-0817% CPU7 nodescluster-0915% CPU7 nodescluster-1012% CPU7 nodescluster-1110% CPU9 nodescluster-1219% CPU5 nodescluster-1319% CPU5 nodescluster-1425% CPU7 nodescluster-1512% CPU7 nodescluster-1613% CPU7 nodescluster-1717% CPU7 nodescluster-1824% CPU7 nodescluster-1914% CPU9 nodescluster-2014% CPU7 nodescluster-2112% CPU9 nodescluster-2217% CPU7 nodescluster-2319% CPU9 nodescluster-2415% CPU9 nodescluster-2518% CPU5 nodescluster-2618% CPU7 nodescluster-2711% CPU5 nodescluster-2828% CPU7 nodescluster-2912% CPU7 nodescluster-3023% CPU7 nodescluster-3121% CPU5 nodescluster-321% CPU7 nodescluster-3315% CPU9 nodescluster-349% CPU7 nodescluster-3518% CPU5 nodescluster-3614% CPU9 nodescluster-3716% CPU7 nodescluster-3814% CPU7 nodescluster-3915% CPU5 nodescluster-4028% CPU5 nodescluster-418% CPU7 nodescluster-4214% CPU7 nodescluster-4322% CPU7 nodescluster-4414% CPU7 nodescluster-4513% CPU7 nodescluster-4611% CPU7 nodescluster-4713% CPU5 nodescluster-4820% CPU7 nodescluster-4911% CPU5 nodescluster-5010% CPU9 nodesEstate before consolidation50 separate clusters of around 7 nodes each, 346 nodes in total, averaging 15.0% CPU utilization.
15%Average CPUAverage CPU CPU utilization15.0% of provisioned CPU is in use.

346 nodes running 415 vCPU of actual work.

The arithmetic, in full
StepWorkingResult
Provisioned today50 clusters totalling 346 nodes (drawn around 7, 5 to 9) x 8 vCPU2768 vCPU
Mean demand2768 vCPU x 15.0% estate average utilization (per-cluster 0.5% to 28.4%, sd 5.3%)415 vCPU
Aggregate peak415.2 vCPU x (1 + (2.23 - 1) / sqrt(50)), a pooled peak-to-mean of 1.174487 vCPU
Consolidated, sized once for the peakmax(3, ceil(487.3 vCPU / (8 vCPU x 37.5% target))) = max(3, ceil(162.44)); the mean sits well under that peak163 nodes, averaging 31.8%
Auto-scaled through the daythe pool follows the pooled curve in whole nodes, 30 minutes behind it, holding its size for 2 hours before shrinking142 nodes on average, at 36.5% CPU
Utilization across the day32.1% to 38.8% against a 37.5% setpoint: the pool runs hot while it's a bucket behind a rise, and cool while the cooldown is still holding capacity after a peak32.1%-38.8%

Assumptions

  • 8 vCPU per node. Standalone clusters are drawn around 7 nodes, snapped to an odd number for quorum and held between 3 and 15; in this estate they run 5 to 9, a 1.3-node standard deviation, for 346 nodes in total.
  • Each standalone cluster's CPU is a draw from a normal distribution centred on 15.0% and held between 0% and 100%; in this estate they run 0.5% to 28.4%, a 5.3-point standard deviation. 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 163 at peak.
  • The auto-scaler sizes for what it saw 30 minutes ago and waits 2 hours before shrinking, so the pool averages 36.5% 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.