feat: speed up CI builds with unity build #2064
Draft
+86
−56
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.
Briefly, what does this PR introduce?
To speed up CI builds, we can use unity builds, essentially bundling multiple source files in a single source file per library, and compiling in one go. This speeds up a non-ccache compilation locally from
to
(Methodology:
rm -rf build && cmake -Bbuild -S. -DCMAKE_UNITY_BUILD=ON -DCMAKE_UNITY_BUILD_BATCH_SIZE=24 --fresh && /usr/bin/time -v make -Cbuild -j8 install
)Unity builds are not without their drawbacks. It requires that the different source files can coexist in a single source file. They cannot define functions with the same name in the same namespace. It is in general a good practice to avoid these conflicts (by defining them once), so in addition to the benefit of faster compilation, this is a useful for the code base quality.
Needs:
operator->
for podio collection objects #2060src/algorithms/tracking
#2062What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No.
Does this PR change default behavior?
No.