Eight idle GPUs. Zero usable slots.

Short video caption

Eight GPUs idle across two domains of four do not make one eight-GPU placement. In Kueue, a required topology can constrain all pods to one domain; cohort quota borrowing is a separate question. This is a simulated cluster, not a provider measurement. Ask for topology-valid queue time, fabric test results and completed useful GPU-hours by job shape before trusting a fleet utilization headline. #EricFieldNotes

Full written post / accessible read

A neocloud dashboard can show eight idle GPUs while your eight-GPU job waits. In this simulated cluster, four free devices sit in one fabric domain and four in another. The job needs eight together. Available inventory is not a valid placement.

The customer sees idle hardware and a growing queue. The operator sees stranded fragments. Adding every free card together will not answer when this job can start, and a high fleet utilization chart will not explain why another job is late.

Kueue can require a pod set to fit in one rack or block and calculates free capacity per topology domain. A queue may borrow quota from a cohort, but borrowed quota cannot create an eight-device domain where only two fragments of four exist. The scheduler needs both policy and placement evidence.

For each workload class, report time to a topology-valid allocation, fabric performance and completed useful GPU-hours. Rehearse your actual job size and placement rule before buying more capacity or promising a start time. Do this because utilization without topology can hide the very shortage customers pay for.

#EricFieldNotes

Evidence and boundary

On-screen boundary: SIMULATED PLACEMENT · KUEUE DOCUMENTED. The sources below support documented mechanisms and specifications; illustrative scenarios are not presented as measured incidents.