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

Performance is not what it could be #110

Open
jxanders opened this issue Mar 29, 2021 · 1 comment
Open

Performance is not what it could be #110

jxanders opened this issue Mar 29, 2021 · 1 comment

Comments

@jxanders
Copy link

jxanders commented Mar 29, 2021

I was testing this repo and then I tested another repo which implements MTCNN in TF2.

I was able to get ~30ish FPS using the linked repo on CPU. Using this repo I can only get 3 FPS with the same images at the same size using the same MTCNN parameters. I am no ML expert, but I believe this is due to how much numpy is used in this repo vs in the other repo which takes advantage of TF's CPU parallelization.

It might be worth looking into the other repo (also MIT) and using their TF model instead of the numpy weights

@do335
Copy link

do335 commented Aug 1, 2022

having the same problem

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

2 participants