feat: add support for parallel kind processing with threads #840
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.
Even with 3.14 free-threaded python, this is still a bit slower than multiprocessing on Linux, but it will allow us to start experimenting with it more, and may allow users on macOS and Windows to immediately see a speed-up.
I did some basic testing of this on macOS in taskgraph; I haven't tested it in the context of Gecko yet outside of Linux. My intention is to turn it off by default for Gecko by setting
TASKGRAPH_SERIALwhen theforkmultiprocessing context is unavailable, and then get some more broad testing before it is enabled by default.I'll also probably wait until #752 in completed before landing this. This should either let me drop the
schema.pychanges altogether (ifmsgspecis threadsafe), or if it's not, there will be a lot of conflicts to deal with, and I don't want to interfere with that work.