~/talk

Scaling AI Workloads with Kubernetes: Sharing GPU Resources Across Multiple Containers

links:none on file
slides:none on file

Kubernetes plus the NVIDIA GPU Operator and device plugin expose GPUs as integer devices so containers can share a card via MIG (up to seven compute slices) or by operator-driven time slicing. MIG physically partitions an A100 into 1/7 compute slices with peculiar allowed sizes (1,2,3,4,7 produce 5/20/40 GB quirks) and often requires a GPU reboot to reconfigure. Time slicing is logical and cheaper to reconfigure but gives variable QoS; Helm, configmaps and node taints/tolerations enforce placement.

AI-written summary · about

  1. 0:00Scaling AI workloads
  2. 3:08Why Kubernetes for GPUs
  3. 4:11Multi-instance GPU (MIG)
  4. 7:19Partitioning GPU slices
  5. 11:36NVIDIA GPU Operator
  6. 14:26Dedicated GPU nodes
  7. 16:13GPU sharing limits
  8. 17:56Sharing GPUs via MIG
  9. 21:05Time slicing GPUs
  10. 23:35MIG vs time slicing
  11. 25:44Optimizing deep learning
  12. 28:12Summary
  13. 28:33Question and answer session
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.