I would also like to point out that all of the above recommendations depend on what you use to compile. For example, if you use the VisualStudio command line, you will be very sad when you try to execute parallel assemblies. Also, how many assemblies will continue if they are parallel. Most people try to build build servers too much, the processor is rarely a bottleneck. Disk I / O is usually the culprit. Do you also need to analyze how much of your assembly can work in parallel, or are these heavy dependency assembly projects in the order type? As a rule, you should have an equipment specialist who analyzes the current assembly (assembly), and they can make recommendations on them. We actually use servers of virtualized buildings (6), all of which work on the same quad core with 4 GB of RAM, and it works almost as fast as when each of them works directly on the server. So we got our parallelism.
source share