Feature/js/parallelize matrix build#211
Merged
ClutchplateDude merged 2 commits intoOpenAstroTech:developfrom Feb 10, 2025
Merged
Feature/js/parallelize matrix build#211ClutchplateDude merged 2 commits intoOpenAstroTech:developfrom
ClutchplateDude merged 2 commits intoOpenAstroTech:developfrom
Conversation
andre-stefanov
previously approved these changes
Dec 13, 2022
julianneswinoga
force-pushed
the
feature/js/parallelize-matrix-build
branch
2 times, most recently
from
2edb3b2 to
b228950
Compare
julianneswinoga
force-pushed
the
feature/js/parallelize-matrix-build
branch
from
b228950 to
20a4bc1
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Linking is a single-threaded task it does not effectively utilize multicore processors. By changing
matrix_build.pyto instead create N projects which each will build a solution in parallel we can avoid the single-core linking bottleneck. This scales very well with the number of processors. Buildingmksgenlv21:Our current GitHub Actions workflow only runs on dual core machines (N=2), so the speedup is marginal (but tangible) but this prepares us well for if we want to run the build process on a more powerful CI.