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

Use multiprocessing instead of multithreading #128

Open
pozitronik opened this issue Nov 15, 2024 · 0 comments
Open

Use multiprocessing instead of multithreading #128

pozitronik opened this issue Nov 15, 2024 · 0 comments
Assignees
Labels
dev 🧑‍💻Developer issues (todos, experiments, styling, etc)

Comments

@pozitronik
Copy link
Owner

Because of the GIL the GUI model does utilize only one CPU core. The processing threads and display thread virtually shares the same process, which leads to visible lags. It doesn't affect that much in the case when ONNX framework is used (it seems it has own multiprocessing implementation), but main processing thread still affects program latency.
Solution: rewrite GUI Model to true multiprocessing support.

@pozitronik pozitronik added the dev 🧑‍💻Developer issues (todos, experiments, styling, etc) label Nov 15, 2024
@pozitronik pozitronik self-assigned this Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev 🧑‍💻Developer issues (todos, experiments, styling, etc)
Projects
None yet
Development

No branches or pull requests

1 participant