[feature] Build packages in parallel
See original GitHub issueWould it be possible for conan to build packages in parallel? Similar to colcon
, which just shows the overall status (Like building packages 4/18
) conan should know the correct order from the overall build tree.
WHY? it would speed up the total process, since many small conan packages do not saturate higher core CPUs with building (cmake, packaging etc is all single core anyways)
- I’ve read the CONTRIBUTING guide.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
[Feature Request] Enable parallel installation of libaray #14664
What I wanted is like vcpkg spawn multiple itself and install independent module simultaneously, just like I manually started multiple vcpkg ...
Read more >Parallel builds in Maven 3 - Apache Software Foundation
This build-mode analyzes your project's dependency graph and schedules modules that can be built in parallel according to the dependency graph of your...
Read more >Parallel Builds | Buildkite Documentation
Running a build's steps in parallel is a way to decrease your build's total running time. This guide will show you how to...
Read more >Vcpkg: introducing installation options with Feature Packages
With Feature Packages you have more control over how you build a library as you can specify different options (features).
Read more >Ability to run several build steps in parallel within a single build
Running several steps in parallel does not solve this problem - you only have 1 MSTest config when using a SLN as the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
hey @lasote , thanks for the heads up. I know about that variable, but as we try to stick to the
conan
philosphy of one library per package, those tend to be very small packages with only a few*.cpp
files, which do not really make my 16 core workstation sweat 😅So the idea would be to use the power to build those small packages in parallel, hiding all the output (which is shown in case a build fails of course) and showing a nice info for the overall progress.
@memsharded we are already using the file-download cache. My assumption is that its not the download cache that is the issue (that has proven to have a good concurrency capability in our CI, as we share the same download cache on the host node with multiple pods running concurrently), but the followup install process that first cleans the dir in the local cache, then unpacks the prebuilt binary and headers.