How do you manage models in distributed Dask
- Dominant language
- Jupyter Notebook
- Stars
- 524
- Forks
- 64
- Avg merge
- 4h 1m
- Merged PRs (30d)
- 3
Description
Hi guys, I really love using Dask as the backbone for this problem but I have a question:
If you use a GPU enabled model for both feature extraction and feature matching, how will the Dask workers manage the GPU memory required for these tasks?
For example, with superpoint https://github.com/borglab/gtsfm/blob/master/gtsfm/frontend/detector_descriptor/superpoint.py it looks like this class will be initialized on all workers? So do you run the risk of running out of GPU memory if your extractor and matcher GPU models are quite large?
Thanks again for the exciting project
Contributor guide
Research direction
Start by reading gtsfm/frontend/detector_descriptor/superpoint.py and the surrounding Dask worker setup. Determine how extractor and matcher models are initialized across workers and document the GPU-memory implications, including what behavior users should expect when models are large.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision, distributed-systems, machine-learning
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100