FIELD NOTE / X
Fairness is a customer promise.
The complete written thought and the evidence behind it. The video edition will follow its public release.
The written argument is here.
This approved X edition is on the journal now. Its video player and original platform link will appear after each public release is verified.
Fairness is a customer promise.
Video caption
Fairness is a customer promise. A burst job may be useful and interruptible. Measure kept start times and useful work together. #EricFieldNotes
Full written post / accessibility read
Kueue can express quotas, cohorts, borrowing and fair sharing. It cannot invent the business promise for three tenants sharing a scarce GPU pool. Who may borrow idle reservation? Who yields when the owner returns? Who pays for restart?
Tenant A pays for a start deadline. Tenant B borrows unused GPUs for a batch. A's workload returns sooner than expected. If the contract never named notice, preemption and checkpoint responsibility, both customers can reasonably feel the platform broke its promise.
Before enabling lending, specify which jobs can borrow, which can be preempted, notice time, checkpoint validation, deadline priority and billing treatment. Replay A's early return in a disposable scheduler and inspect actual placement and recovery receipts.
Track utilization beside missed start promises, restart cost and accepted tenant work. Do this because maximizing occupancy without a reclaim contract merely hides the cost in somebody else's queue.
#EricFieldNotes
Four-beat scene transcript
1. Fairness is a customer promise.
Kueue can express quotas, cohorts, borrowing and fair sharing. It cannot invent the business promise for three tenants sharing a scarce GPU pool. Who may borrow idle reservation? Who yields when the owner returns? Who pays for restart?
Visual: A queue name cannot decide who yields capacity.
2. Idle capacity tempts a hidden tradeoff.
Tenant A pays for a start deadline. Tenant B borrows unused GPUs for a batch. A's workload returns sooner than expected. If the contract never named notice, preemption and checkpoint responsibility, both customers can reasonably feel the platform broke its promise.
Visual: A burst job may be useful and interruptible.
3. Write the reclaim state machine.
Before enabling lending, specify which jobs can borrow, which can be preempted, notice time, checkpoint validation, deadline priority and billing treatment. Replay A's early return in a disposable scheduler and inspect actual placement and recovery receipts.
Visual: Eligibility, warning, checkpoint, deadline, compensation.
4. Sell explicit fairness.
Track utilization beside missed start promises, restart cost and accepted tenant work. Do this because maximizing occupancy without a reclaim contract merely hides the cost in somebody else's queue.
Visual: Measure kept start times and useful work together.
Research and claim limits
- Kueue overview (S124)
The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.