-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slow inference of bottom-up models #138
Comments
Inference speedup is on our list #9 (comment) |
For higher inference speed, you may try to set |
maybe we should add a section in doc to explain how to set flags to enable fast demo, and how to set them to get accurate demo. |
I divided the number of frames by the entire 'while' loop time, so fps is calculated more accurately. standard config - 2.4 fps However, when I use flip_test=False get the following error: Traceback (most recent call last): |
Aha. Sorry for that, this is indeed a bug. |
OK, now it works. Thank you. I was able to get 17.5 fps and even over 22 with visualization off and no imshow. It is a huge difference in speed. Any idea about precision change? |
Yes, speed and accuracy are important trade-offs. Generally speaking, no flip-testing will lead to about 5 mAP drop on COCO dataset. You may follow the guidelines and evaluate the models on COCO. |
Well, I just compiled OpenPose and it runs at around 46 fps (no hand and face detection). The thing is it uses close to 100% of my GPU, while mmpose just uses a fraction of it...(as reported by nvidia-smi) |
Hey @Witek- , @jin-s13 @innerlee |
…sTestCase (open-mmlab#138) * [Enhancement] Provide MultiProcessTestCase to test distributed related modules * remove debugging info * add timeout property * [Enhancement] Refactor the unit tests of dist module with MultiProcessTestCase * minor refinement * minor fix
Where is the config file ? |
I am getting very slow performance on a single person video on RTX2080Ti with the following command
python demo/bottom_up_video_demo.py configs/bottom_up/resnet/coco/res152_coco_512x512.py res152_coco_512x512-364eb38d_20200822.pth --video-path demo/tabata1_640x360.mp4 --show --device cuda:0
FPS ~2.5. It was calculated as total processing time divided by the number of video frames, so it is not super precise...
Any idea what might be wrong?
The text was updated successfully, but these errors were encountered: