project-hami/hami

Heterogeneous GPU Sharing on Kubernetes

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 25 minutes ago
Added to GitGenius on September 15th, 2026
Created on September 14th, 2021
Open Issues & Pull Requests: 54 (+0)
GitHub issues: Enabled
Number of forks: 829
Total Stargazers: 4,644 (+0)
Total Subscribers: 27 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.3 hours
Mean response time: 9.3 days
90th percentile: 5.8 days
Tracked items: 945

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 7% of issues opened in the past year have never received a reply. 85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 94% of issues opened in the past year have since been closed. Three people close 65% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 33
New in 7 days: 23
Closed in 7 days: 14
Avg open age: 72 days
Stale 30+ days: 3
Stale 90+ days: 0

Recent activity

Opened in 7 days: 21
Closed in 7 days: 12
Comments in 7 days: 3
Events in 7 days: 7

Top labels

  • kind/bug (450)
  • kind/feature (173)
  • Stale (165)
  • good first issue (74)
  • kind/design (28)
  • issue/stale (11)
  • kind/cleanup (10)
  • kind/documentation (3)

Detailed Description

HAMi is a Kubernetes device plugin and scheduler extender that enables GPU virtualization and heterogeneous accelerator sharing on Kubernetes clusters.

AI infrastructure teams typically allocate entire GPUs to small workloads, leading to poor utilization and resource contention. HAMi solves this by inserting a virtualization layer between Kubernetes and accelerator hardware. It uses a mutating webhook to intercept pod specifications, a scheduler extender to place workloads with device-aware policies, and device plugins paired with in-container virtualization components to enforce memory and compute isolation. Workloads request fractional accelerator resources through standard Kubernetes resource requests, and the tool coordinates scheduling, allocation, and per-workload limits without requiring application code changes.

HAMi suits shared AI clusters running multi-tenant notebook, training, and inference workloads where GPU utilization is a concern. It is particularly valuable for teams operating heterogeneous accelerator environments spanning NVIDIA, Ascend, Cambricon, Hygon, Iluvatar, Kunlunxin, MetaX, Moore Threads, and other vendors, since it provides a unified scheduling and allocation workflow across different device types and operational models. The tool integrates with standard Kubernetes schedulers like kube-scheduler and Volcano, and includes production-ready features such as metrics, dashboards, a web UI, and Helm-based installation.

The project maintains active development across multiple areas. Device support is regularly expanded to cover new accelerator vendors and models. The codebase receives ongoing refinement in core scheduling logic and isolation mechanisms. Documentation is kept current across multiple languages. Community engagement appears consistent through issue triage and feature requests. The project operates as a CNCF Incubating initiative with established governance and landscape recognition.