← Lab
gpuoversub
confirmedKubernetes · minikubeCluster & infrastructureJuly 8, 2026
the question
What is Kubernetes GPU time-slicing, really?
what came out
Just the scheduler bin-packing an integer it can't see through: one GPU advertised as K units co-schedules exactly K 'dedicated'-GPU pods (there's no device-identity field in the API), and GPUs are integer-only with request==limit forced, unlike CPU. Real minikube, pre-registered, verified.
method & receipts
- Result: confirmed
- Pre-registered — the prediction was written down and committed before the run.
- Reproducible — one script re-runs the whole thing from scratch.
- Independently reviewed — an adversarial review pass, kept in the repo.
- Machine-readable claims — every reported number, in a checkable file.
- Tested — a correctness/benchmark suite ships alongside the code.
→ read the code and re-run it
github.com/v-code01/gpuoversub