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

increase performance #12

Open
PaulaScharf opened this issue Mar 24, 2021 · 3 comments
Open

increase performance #12

PaulaScharf opened this issue Mar 24, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@PaulaScharf
Copy link
Collaborator

Currently the visualization is delayed and runs only at about 3 frames per second. It should be investigated if this can be improved.
One possible approach could be adjusting the networking.

@PaulaScharf
Copy link
Collaborator Author

PaulaScharf commented Mar 24, 2021

I added an option to not use the depth image. This decreases the computation time from ~0.33 seconds to ~0.14 seconds per frame. However, this also means no visualization or logging of hand height. So this approach should only be optional and further means to improve performance have to be investigated.

@PaulaScharf PaulaScharf added the enhancement New feature or request label Mar 29, 2021
@PaulaScharf
Copy link
Collaborator Author

PaulaScharf commented Apr 1, 2021

When I directly show the frame (cv2.imshow(...)) while also sending the frame to the client there is no temporal difference between the client and the direct visualization of the frame. This leads me to believe that there is no delay being caused by the network. This implies that all latency is caused from reading the frame from the camera.

Edit:
Now that we are using usb3.0 again, reading the frame is now possible in under 0.01 seconds. Furthermore it became apparent, that there are other causes of latency as well. Will be investigated.

@PaulaScharf
Copy link
Collaborator Author

PaulaScharf commented May 6, 2021

A big performance eater was the usage of the function "where" from numpy. I replaced every occurence, which resulted in double the framerate.

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

No branches or pull requests

1 participant