FIELD NOTE / INSTAGRAM
High utilization can hide a missed 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 Instagram edition is on the journal now. Its video player and original platform link will appear after each public release is verified.
High utilization can hide a missed promise.
Video caption
High utilization can hide a missed promise.
The rule may still be the wrong customer contract.
Utilization and promise adherence by customer class.
Borrow only with a tested reclaim path.
#EricFieldNotes
Full written post / accessibility read
A GPU fleet lends reserved but idle capacity to a burst tenant. The utilization line rises. Then the reserved tenant returns and misses its start promise because the borrowed work was not recoverable on time. The graph needs both lines.
A quota system can allow borrowing, but the operator must choose preemption rights and notice. If B's job cannot checkpoint and A's start has a hard deadline, lending that exact slot may be commercially wrong even if it increases utilization.
In a test pool, activate reservations while other tenants borrow. Record the promised start, actual start, preemption notice, checkpoint validity, resumed progress and billed time. Break results out by reserved, burst and interruptible service class.
Write the sharing rule, test an early reservation return and publish the recovery terms. Do this because available idle GPUs are only lendable when the eventual owner can still receive the service they purchased.
#EricFieldNotes
Four-beat scene transcript
1. High utilization can hide a missed promise.
A GPU fleet lends reserved but idle capacity to a burst tenant. The utilization line rises. Then the reserved tenant returns and misses its start promise because the borrowed work was not recoverable on time. The graph needs both lines.
Visual: Sharing needs a deadline ledger.
2. The scheduler followed the configured rule.
A quota system can allow borrowing, but the operator must choose preemption rights and notice. If B's job cannot checkpoint and A's start has a hard deadline, lending that exact slot may be commercially wrong even if it increases utilization.
Visual: The rule may still be the wrong customer contract.
3. Overlay two time series.
In a test pool, activate reservations while other tenants borrow. Record the promised start, actual start, preemption notice, checkpoint validity, resumed progress and billed time. Break results out by reserved, burst and interruptible service class.
Visual: Utilization and promise adherence by customer class.
4. Optimize the whole contract.
Write the sharing rule, test an early reservation return and publish the recovery terms. Do this because available idle GPUs are only lendable when the eventual owner can still receive the service they purchased.
Visual: Borrow only with a tested reclaim path.
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.