~/talk

Vendor-Neutral GPU Observability for Kubernetes

links:none on file
slides:none on file

GPU observability unifies vendor metrics by instrumenting scheduling rather than scraping drivers: HAMi records scheduling-layer instrumentation and reports per-workload allocation efficiency, utilization and memory pressure across NVIDIA, AMD, Ascend and any device-plugin accelerator. It injects a device config via a mutating webhook + runtime shim, normalizes vendor counters with adapters and exposes scheduler metrics (reserved vs used memory, sharing, noisy neighbour signals). Project is CNCF incubation with six+ case studies and active vendor adapters and vGPU monitors.

AI-written summary · about

  1. 0:00Introduction to GPU observability
  2. 1:25Vendor-specific GPU metrics challenges
  3. 3:09GPU vs CPU scheduling differences
  4. 4:36Karmada scheduler role explained
  5. 6:42Harmoni metrics enrichment process
  6. 8:29Key workload metrics to monitor
  7. 10:55Standardizing metrics with Prometheus
  8. 12:20Vendor contributions and limitations
  9. 14:29Normalizing metrics across devices
  10. 15:52Dynamic Resource Allocation status
  11. 16:56Project status and community
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 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
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
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.