added support for building core packages in parallel with ryon #874
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nick1udwig
approved these changes
Oct 17, 2025
Member
nick1udwig
left a comment
nick1udwig
left a comment
There was a problem hiding this comment.
Really nice, thanks for the PR ⚡
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
I doing some work on core and got tired of waiting to rebuild after each fix (there were ways to make it easier but I just stuck with it).
Solution
Solution was elegant: substitute the iterator method call from `into_iter' to 'into_par_iter' (from the rayon crate), which handles the parallel execution under the hood. Tested it and with no special flags (you can specify the number of cores) got a 2x speedup in the build-package script time (from 6 minutes to sub 3 minutes on a re-build).
Testing
Could be made default but for the PR I left is as an optional flag.
Docs Update
Reflected in README
Notes
This was downstream of me just asking an LLM client to 'make it faster'. I wonder if we could apply the same principle to other places in our codebase that have long build times,