About NVIDIA's MIG question
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 554
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 14
Description
openpai supports nvidia's A100 and A30 and MIG functions. After my 100 A100 is split using MIG, the job is still scheduled to the entire A100
openpai version：v1.7.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior on OpenPAI v1.7.0 with an A100 or A30 partitioned using NVIDIA MIG, then inspect how the scheduler discovers and allocates GPU resources. Done means a job is scheduled to the requested MIG partition rather than the entire physical GPU, with the behavior verified in a regression test or documented reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100