livepeer / livepeer/go-livepeer
Specifying -nvidia 0 results in GPU 1 being selected -nvidia 1 selects GPU 0
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
**Describe the bug**
Specifying -nvidia 0 results in GPU 1 being selected -nvidia 1 selects GPU 0
**To Reproduce**
Steps to reproduce the behavior:
1. Add -nvidia 0 to start command
2. Start Livepeer
3. View console output and observe "Transcoding on these Nvidia GPUs: [1]" Also confirmed in use that the incorrect GPU is selected and used for transcoding.
4. This behavior also happens in reverse. -nvidia 1 selects GPU 0.
**Expected behavior**
The GPU specified by the -nvidia flag should choose the GPU specified.
**Desktop (please complete the following information):**
- OS: WIndows 10 and Windows Server 2019
- Version Livepeer 0.5.24 - 0.5.27 (probably other versions as well but I have tried it on these versions)
**Additional context**
The behavior is present using both combined O+T and stand alone T configurations
I have not tried this on machines with more than 2 GPUs so I don't know what happens if -nvidia 2 is specified
Contributor guide
Assessment
This issue has not been assessed yet.