Skip to content
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

Intuition of workaround #3

Open
eraserpencil opened this issue Aug 2, 2019 · 0 comments
Open

Intuition of workaround #3

eraserpencil opened this issue Aug 2, 2019 · 0 comments

Comments

@eraserpencil
Copy link

Hi! Thanks for the C++ port of tf-pose-estimation.

I manage to get an average of 6-6.5FPS on a video stream from ZED camera, both running on ROS on a TX2 with TF1..0. That compared to 5-5.5FPS with the original Python implementation (I'm unsure how the original author managed to get ~10FPS with the same setup)

Was wondering how'd the intuition behind the workaround came about. I'm new to Deep Learning and was hoping to squeeze out more performance. Would you know if the performance would just cause a slow startup time or it would affect runtime performance as well. How muxh different would it be to have TensorRT with this as compared to the python implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant