-
Notifications
You must be signed in to change notification settings - Fork 35
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
Issue with built-in multi-threading #158
Comments
You can use the built-in key-value store: https://www.pipeless.ai/docs/docs/v1/kvstore |
You can also ensure those hooks where you process the data are stateful so they sort the frames before running the hook: https://www.pipeless.ai/docs/docs/v1/getting-started#stateless-vs-stateful-hooks |
Are reading and writing to the built-in key-value store thread safe ? |
Yes, it is |
When I tried to make the
facing the below error from the onnx runtime. It runs fine when used in stateless mode. (I am using a YOLOv8 object detection model (onnx) in
Any idea why would this happen ? |
If you are using an ONNX model for process, I would recommend using a Could you give a try with that setup? |
Hi,
In the readme, it is mentioned that Pipeless does multi-threading by default. When I am trying to use variables/lists in the post process that are updated across frames (for example, frame count, moving average of predictions from frames), I am running into race conditions. It messes up the calculations that use these variables/lists that are accumulated over a period.
What is the best way to handle this situation and ensure thread safety ?
The text was updated successfully, but these errors were encountered: