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

ONNX Runtime Multithreading Issue Preventing NIST FRVT 11 Submission #126

Open
AwaisPF opened this issue Feb 28, 2024 · 2 comments
Open

Comments

@AwaisPF
Copy link

AwaisPF commented Feb 28, 2024

Reporting a Multithreading Issue in ONNX Runtime to NIST FRVT GitHub Repository

Body:

I am encountering an issue with ONNX Runtime that prevents my submission to the NIST FRVT 11 evaluation.

Describe the problem:

  • I am using ONNX Runtime for inference in my submission package.
  • I have attempted to restrict the number of threads used by ONNX Runtime to 1 using the provided GUID.
  • However, when my submission package is executed, the NIST FRVT script detects 17 threads instead of the expected 2.
  • This discrepancy becomes apparent when using the top -H command, which reveals 17 threads are created, with only 1 in a running state and the remaining 16 in a sleeping state.
  • Due to this multithreading behavior, my package crashes when executed by NIST FRVT on multiple cores, violating their single-threaded requirement.

Here is screen shot of htop of same package
Screenshot 2024-02-28 at 7 03 14 PM

  • Only one thread is running but why there are so many threads launched

Possible impact:

  • This issue prevents my package from being successfully evaluated in the NIST FRVT 11 program.

  • I kindly request the NIST FRVT developers to investigate this multithreading issue in ONNX Runtime and provide any potential solutions or workarounds.

  • Additionally, I would appreciate guidance on overcoming this limitation and ensuring successful submission compliance with the single-threaded requirement.

Additional information:

  • Version of ONNX Runtime==1.10.0

Closing:

Thank you for your time and consideration. I look forward to your response and assistance in resolving this issue.

@deeperlearner
Copy link

deeperlearner commented Mar 15, 2024

Did you close the docker and re-open one?

@AwaisPF
Copy link
Author

AwaisPF commented Mar 25, 2024

there is no usage of docker here. It ran directly on host machine as recommended.

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

No branches or pull requests

2 participants