DeepLabCut / DeepLabCut/DeepLabCut-live-GUI
GenTL backend interferes with PyTorch when running in the same process
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 72
- Forks
- 28
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
Performance heavily degrades on some machines when using the GenTL backend and running torch tasks.
This is solved by moving the GenTL or torch work into a different process.
It should be carefully researched whether moving the torch or GenTL processes outside of the main process would be better.
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 performance degradation when the GenTL backend and PyTorch tasks run in the same process. Compare this with moving either workload to a separate process, then document which arrangement avoids the slowdown and under what machine conditions. Done means the preferred process boundary and supporting evidence are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100