Comparing C/C++ unity build with regular build on a large codebase (2024)

PaulHoule 11 points 2 comments April 01, 2026
hereket.com · View on Hacker News

Discussion Highlights (2 comments)

pstomi

By reading your initial script,I see that there was absolutely no parallelisation in the initial build. Was it a choice because you wanted to compare only single core performances?

jjmarr

If you're doing single-core builds, you will get impressive speedups from unity builds. This is because C++ compilers spends a lot of time redundantly parsing the same headers included in different .cpp files. Normally, you get enough gains from compiling each .cpp file in parallel that it outweighs the parsing, but if you're artificially limited in parallelism then unity builds can pay for themselves very quickly as they did in the article. C++20 modules try to split the difference by parsing each header once into a precompiled module, allowing it to reuse work across different .cpp files. Unfortunately, it means C++ compilation isn't embarrassingly parallel, which is why we have slow buildsystem adoption.

Semantic search powered by Rivestack pgvector
3,471 stories · 32,344 chunks indexed