Difference between revisions of "Inference Inside OpenCV or Dlib"
Line 6: | Line 6: | ||
The other reason why we don’t want to perform inference in the frame processor is for modularity.<ref>https://en.wikipedia.org/wiki/Modularity</ref> Flexibility is important because it's often more feasible for relatively lightweight things like frame logic etc. to be done on one machine (like a Raspberry Pi) but for the heavy lifting like DNN inference to be offloaded to some external and much more powerful machine. It also lets us avoid putting put all our eggs in one OpenCV or Dlib basket. | |||
==References== | ==References== | ||
<references /> | <references /> |
Revision as of 13:40, 13 October 2019
Reasons Not To Perform Inference With OpenCV's or Dlib's DNN
OpenCV’s DNN will accept TensorFlow models and pytorch models but it seems like there are problems getting it to use CUDA and NVIDIA's GPU’s[1][2] which is one of the reasons why we use an external neural network server
Dlib’s DNN can use Nvidia GPU’s internally but can’t import any models but its own.[3] So no TF, Pytorch or even Caffe.
The other reason why we don’t want to perform inference in the frame processor is for modularity.[4] Flexibility is important because it's often more feasible for relatively lightweight things like frame logic etc. to be done on one machine (like a Raspberry Pi) but for the heavy lifting like DNN inference to be offloaded to some external and much more powerful machine. It also lets us avoid putting put all our eggs in one OpenCV or Dlib basket.