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
75 nodes running 90 vCPU of actual work.
The arithmetic, in full
| Step | Working | Result |
|---|---|---|
| Provisioned today | 5 clusters of 15 nodes each, 75 in total x 8 vCPU | 600 vCPU |
| Mean demand | 600 vCPU x 15.0% estate average utilization (per-cluster 6.5% to 25.9%, sd 7.0%) | 90 vCPU |
| Aggregate peak | 90.0 vCPU x (1 + (2.23 - 1) / sqrt(5)), a pooled peak-to-mean of 1.549 | 139 vCPU |
| Consolidated, sized once for the peak | max(3, ceil(139.4 vCPU / (8 vCPU x 37.5% target))) = max(3, ceil(46.48)); the mean sits well under that peak | 47 nodes, averaging 23.9% |
| Auto-scaled through the day | the pool follows the pooled curve in whole nodes, 30 minutes behind it, holding its size for 2 hours before shrinking | 32 nodes on average, at 35.2% CPU |
| Utilization across the day | 22.9% to 41.6% 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 peak | 22.9%-41.6% |
Assumptions
- 8 vCPU per node. Standalone clusters are drawn around 15 nodes, snapped to an odd number for quorum and held between 3 and 15; in this estate they're all 15, because a spread centred on the end of that range has nowhere to go, for 75 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 6.5% to 25.9%, a 7.0-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 47 at peak.
- The auto-scaler sizes for what it saw 30 minutes ago and waits 2 hours before shrinking, so the pool averages 35.2% 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.