-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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 Classification #52
Comments
Hi @aaaaalucard - thanks! My guess is that the web demo doesn't have to re-start when classifying, but every time the classification demo is started, it spends a few seconds loading a large model in a Lua/Torch subprocess. We're interested in moving the subprocess to a server that the Python scripts can communicate with in #4. We probably won't make this change for a few months and are happy for help if you're interested. The performance differences could also be due to image sizes. And something like #50 might slightly improve the performance for everything. I'm closing this issue and delegating the improvements to #4 and #50 for now. -Brandon. |
I did as Bamos advised and as he guessed the most of the time (at least on my machine) is due to libraries and Openface models: ./demos/classifier.py --verbose infer ./classifier.pkl image_to_classify.jpg > classifier_output.log real 0m2.883s cat classifier_output.log How can make you merge the additions i made do classifier.py? |
Hi @lucafeudi - thanks! Can you send in a pull request? |
@bamos Hey Brandon, nice project! Our team are really interested and currently we are developing a real time video analyzing tool.
One question i have is that when i try to use the classifier.py to make a prediction, it may take couple of seconds to get the result, and i noticed it is slower than the web demo.
Are those two classification methods different? Is there any way to speed up calling classifier.py, like small photos for example?
The text was updated successfully, but these errors were encountered: