-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
FPS issue with movenet_lighning_int8 on docker container #864
Comments
Could you try the cropping algorithm mentioned in official documentation and see if it enhances the FPS and prediction quality. Thank you! |
ok, i will try this, but the point is that with the same code, movenet thunder works with 15-16 fps and movenet Lightning int 8 works at only 1 fps. It's not normal, i think. |
@singhniraj08 , On pc stock or in a docker container the thunder model returns much più fps then other model. |
I was unable to run your code as the input video file didn't worked for me. I tried running the example notebook on TFHub site and observed that both lightning and thunder performs at ~4 FPS. Please find attached gist here. As per this TF blog, this model achieves 30+ FPS by running the model completely client-side, in the browser using TensorFlow.js with no server calls needed after the initial page load and no dependencies to install. @alenarepina, Can you please share some insights on why lightning performs at ~ 4 FPS while running on colab with GPU Thank you! |
Closing due to inactivity. |
What happened?
Hi everyone, i'm trying to test the performance of different pose estimation models over a raspberry and over a docker container on pc. I measure FPS and Accuracy.
I have an issue on movenet_lightning_int8 on pc docker container. This model processed only 1 frame for second, worst than movenet thunder. Why?
Relevant code
Relevant log output
tensorflow_hub Version
0.12.0 (latest stable release)
TensorFlow Version
2.8 (latest stable release)
Other libraries
No response
Python Version
3.x
OS
Linux
The text was updated successfully, but these errors were encountered: