FIX: Make global queue objects thread-local #2846
Open
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Description
Sycl queues on GPU are managed through global objects, but since the introduction of array API, some operations might be offloaded to other libraries that raise the GIL during their operations, and might thus lead to conflicts if sklearnex objects are used in parallel through python threads instead of being in separate processes.
This PR fixes potential thread racing issues by making the queues thread-local, with a helper class as suggested by @ahuber21 .
Checklist:
Completeness and readability
Testing