ci(ENG-21467): Make build-cpp even faster.
#24452
Closed
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.
What does this PR do?
Throws more jobs at
cmakethancmakethinks it should use. Sincecmakeis oblivious to the fact that it's very likely going to hit a 100% hit rate, we need to throw more cores at it so that all the cache requests are made in parallel.How did you verify your code works?
I ran CI with different job multipliers and compared the performance of each:
FTC - Fail-to-cache https://linear.app/oven/issue/ENG-21502/x64-and-aarch64-linux-targets-failing-to-use-sccache
At high job multipliers, windows crashed due to high contention on the
sccachelock-file in S3. I don't know why that happens.Based on this plot, there is no appreciable difference in parallelizing the job, unfortunately