-
Notifications
You must be signed in to change notification settings - Fork 2
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
Why not multithreading? #6
Comments
I could use multithreading if the two tasks were internal to the same process. But even then "compose" thread should still wait for the outcome of the "compute mask" thread, unless I calculate the "previous" mask... but I can improve socket communication with a more performant protocol as zerorpc (it builds on top of ZeroMQ and MessagePack), instead of bloated http protocol. |
Yes, indeed I meant a single process with two threads. This would imply porting the bodypix process to python. Not the easiest task, indeed. |
I would suggest to change the socket communication to multithread processing, with a thread that computes the mask and the other that composes the mask with the background.
The overall computation speed and overload should improve dramatically.
The text was updated successfully, but these errors were encountered: