davisking/dlib

Choose backend (GPU/CPU)

Open

#1,852 opened on Jul 31, 2019

View on GitHub
 (12 comments) (1 reaction) (0 assignees)C++ (3,314 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (12,570 stars)
PR merge metrics
 (Avg merge 3h 56m) (2 merged PRs in 30d)

Description

So I couldn't find a way to do this in the documentation but I was wondering if there was a way to force dlib to use the CPU if it's built with CUDA enabled? I ask because I'm making a multithreaded application with dlib and only a maximum of 2 threads at a time can use CUDA (because of limitations of the GPU itself). So I'd like to in a thread get dlib to use the GPU in the thread if <2 threads are using the GPU and otherwise fallback to using the CPU.

Also a slightly related question how would dlib cope with a machine with multiple GPUs installed all for compute purposes?

Contributor guide

Research direction
Investigate dlib's CUDA support and device selection mechanism. Look for existing runtime configuration options or propose a new API to switch between GPU and CPU backends.
Tech stack
cpp
Domain
machine learningbackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++CUDA
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30