Cloud cost
Workload idle
Capacity that a pod requested and had reserved but does not use. It is a request-sizing problem, fixed by sizing to observed usage.
Last updated
Definition
Workload idle is the gap between what a pod requested, and had reserved for it, and what it uses. The reservation drives node count and cost. Unlike cluster idle, this waste belongs to one workload whose request is too high for its real usage. The fix is to pull actual P95 usage and size the request down to it. Leave a margin of headroom. Do not size to the bare observed average.
Datadog's State of Containers and Serverless research found that most workloads use under half of their requested memory and under 25% of their requested CPU. That is the gap this term names.
Where it shows up
Workload idle shows up as the gap between a pod's requested resources and its observed usage. The request is visible in its manifest. The usage is tracked in a monitoring tool over time. Kubernetes only records the request. The usage side comes from whatever metrics pipeline the cluster runs.
What makes it expensive
Teams set a request from a rough guess or a legacy default and never revisit it. The real usage becomes known and the traffic settles into a stable pattern. The request stays put. Pull P95 usage over several weeks, not one quiet day. Compare it with what the manifest reserves.
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
- Bin packing
- 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.