Cloud cost
Bin packing
How tightly a scheduler packs pods onto the fewest nodes possible, given their requests. Loose packing strands capacity as cluster idle across many half-empty nodes.
Last updated
Definition
Bin packing describes how densely a scheduler consolidates workloads onto available nodes. A scheduler (or a cluster-autoscaler / Karpenter configuration) that spreads pods thin across many nodes, rather than consolidating them tightly, leaves each node with unused, schedulable capacity that nothing is using: cluster idle, multiplied by however many nodes are running below a useful packing density.
Packing density interacts directly with node shape: the same total requested capacity can be served by many small, loosely-packed nodes or fewer, larger, tightly-packed ones. The latter usually strands far less capacity per dollar of node cost.
Where it shows up
Bin packing shows up as node count and per-node utilization in a cluster dashboard: the same total requested capacity served by many lightly-loaded nodes versus fewer, more tightly packed ones. A cluster-autoscaler or Karpenter configuration file sets the packing behavior directly, alongside the node shapes it's allowed to choose from.
What makes it expensive
An autoscaler configured to spread pods thin rather than consolidate them strands schedulable capacity on every node it starts. The cluster looks busy while paying for a lot of room nothing ever asked for. Total requested capacity can look entirely reasonable at the same moment average node utilization sits low, and those two numbers disagreeing is the whole problem.
Related
More in Cloud cost
- Committed use discount (CUD)
- Reserved instance (RI)
- Savings plan (SP)
- On-demand vs. spot instances
- Data egress
- Amortized, blended, and unblended cost
- Billed vs. effective vs. list vs. contracted cost
- Rightsizing
- Idle and orphaned resources
- Storage class
- Lifecycle policy
- Incremental snapshot
- Allocatable capacity
- Requests vs. limits
- Cluster idle
- Workload idle
- Cost allocation tags
- Tag coverage
- Unallocated spend
- Showback vs. chargeback
- Unit economics
- RI/SP coverage and utilization
- Observability tax
- Metric cardinality
- High-water-mark billing
- Log ingest vs. index
- Snowflake credit
- Auto-suspend / resume minimum
- BigQuery slot
- Bytes scanned & partition pruning
- Time Travel & Fail-safe
The meter you don't watch still grows.
Waste rarely hides in the service you check every week. CostMon watches every meter on your stack, including the ones you forgot were running.