Removing the per process file flag to reduce the llvm filemerge time#9449
Merged
sylvestre merged 1 commit intouutils:mainfrom Nov 22, 2025
Merged
Removing the per process file flag to reduce the llvm filemerge time#9449sylvestre merged 1 commit intouutils:mainfrom
sylvestre merged 1 commit intouutils:mainfrom
Conversation
Collaborator
Author
|
Went from around 27 minutes to around 8 minutes: https://github.com/uutils/coreutils/actions/runs/19600074415/job/56130291656?pr=9449 Most of the time is actually in the tests themselves now since they don't all run in parallel. Still a bunch of work to do in speeding up the tests themselves especially in the tail and timeout package. The open timeout PR should reduce this number even more. |
|
GNU testsuite comparison: |
Contributor
|
kudos! |
Contributor
|
seems that it fixed #9059 |
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
2 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.
I've been working on trying to increase the code coverage and I was finding that it takes around 30 minutes for the build suite to collect this data and that the majority of the time is spent on merging the llvm profile data files. When doing some investigation on this there was a post that mentioned that having %p has the potential to increase the file count by a factor of 1000x and since we were merging the files anyways there was no need to use this flag.
Running this on the build fleet to see if the outputs are the same and if the time is radically different