2 fps for demos on CUDA 12.6 #128
Assignees
Labels
nvidiaproblems
NVIDIA/CUDA problems with host system
tensorflow problems
Problems caused by the tensorflow framework
Comments
|
Updated to mnet4 and TensorFlow 2.18, still the same, 2fps. 😭 |
|
https://www.tensorflow.org/install/pip But it seems to work on CPU only: |
|
Dear friend, The problem you are experiencing is from either :
MocapNET is a very tiny network and can run on CPU alone fast enough providing 2D joint to BVH output. This is not the case for the network that goes from RGB image to 2D joints that does convolutions which is computationally much heavier and needs a GPGPU accelerator. Your 2fps slow performance is happening because the RGB->2D joints network runs on CPU causing the slow down. In the dependencies/ subdirectory you have a tensorflow version compiled for CPU or compiled for GPU but for another combination of CUDA/CUDNN etc. In fact when GPU acceleration is available what happens is that RGB -> 2D joint estimation runs on GPU while 2D joint to BVH estimation (for the previous frame) is running on CPU. Now having explained the design and issue, in terms of making sense of versions etc, this is a list of the official "expected" version compatibilities: For example tensorflow-2.14.0 expects CUDNN 8.7 and CUDA 11.8 It should also be noted that you can have multiple versions of CUDA on your system :
You can select which one is 'active' if I change export PATH=$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/cuda/bin and replace cuda with cuda-10.0 then tensorflow will be able to be ``linked against this'' in the next builds etc. If you look at the logs you attached to the tickets : W0000 00:00:1731007916.405884 179300 gpu_device.cc:2344] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform. So tensorflow is not finding the versions it is expecting and skipping using GPU devices. So unfortunately these problems have to do with versioning and more specifically Tensorflow VS NVIDIA. To mitigate this problem for mnet4 I overhauled the whole codebase to transition it to python so that it makes it easier using pip to install everything at once at a virtual environment instead of having to compile / download everything manually, https://github.com/FORTH-ModelBasedTracker/MocapNET/tree/mnet4/src/python/mnet4 maybe if you make a seperate git clone of the mnet 4 and navigate to src/python/mnet4/ using this script To also have an idea on how the python stuff works I have a Google collab notebook setup Hope I helped, please note that all of this situation is not a problem of the MocapNET codebase but of its Tensorflow dependency! |
AmmarkoV
added
the
tensorflow problems
|
I'm trying to understand what I did wrong. On ment4/, I manually downloaded Tensorflow 2.18 with GPU for python 3.10(.12) (python --version, since it's what python --version throws) from https://www.tensorflow.org/install/pip Here's and If you know a way to show more info, please let me know. Could you please make a freeze > requirements.txt when you use Cuda 12, to see what I have wrong? Just another question related to the error above: This directory exists in my setup: So why does Here's a full initialize & build log: |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After reading #114, downloading, unzipping and re-initializing (for the 7th time) I still get very low speed.
Live (webcam) demo:
Same on webm file demo:
It's the 2D joint detector
I also re-initialized with ENABLE_OPENGL=ON, on Ubuntu 22.04
Initialize logs:
What should I do to get a better speed? Thank you :)
The text was updated successfully, but these errors were encountered: