RSS Feed
Knowledgebase : IncrediBuild for Windows > Performance
This issue only occurs for builds executed when using the BuildConsole /command or ibconsole /command. This is because the VBCScompiler only has AllowIntercept="true" in the build profile when the build is executed from within Visual Studio.    To sol...
The main Benefits of IncrediBuild for Build Servers are the following:  * With IncrediBuild installed on other machines, the build server power is dramatically increased since it can use more cores for the build process by harnessing idle CPU cores on...
Although in some scenarios incremental builds are short and won't get the same benefits from IncrediBuild as a full rebuild, you should be aware that this is not always the case. When a change is made to core projects (projects that other projects depen...
If the build has large tasks – there is basically no limit for the cache file size since it will damage the build.  However, once the build finish, the main Coordinator will monitor the cache size on all Agents and reduce it to the defined limit. This o...
The following hardware characteristics have a significant impact on the performance of IncrediBuild Agents (in order of biggest impact):  1. Multiple cores allow IncrediBuild Agents to utilize each core in parallel to execute multiple processes. Modern d...
In principle up to 400 Agents can be used with one single Coordinator (this is a "safe" figure; the real number is higher). When an Incredibuild build is running, the Coordinator's default behavior is to employ up to 12 Agents concurrently at any one poin...
Until version 4.0 IncrediBuild might, in some cases, take longer than Visual Studio to execute the link phase. This is related to the fact that IncrediBuild generated multiple PDB and IDB files when building (one for each concurrent Agent), while Visual S...
If the build has no dependencies but it still looks like this:        It may be related to different output folders under:  C/C++ > Output Files > Object   If the option chosen is: "$(IntDir)%(RelativeDir)"  the above build result will be achi...
This is regular behavior when executing builds with MSBuild rather than Devenv.   This is not related to IncrediBuild.    Starting your build with pre and post build steps when executing wth MSBuild will cause these steps to rebuild regardless of wh...
Our general recommendation is actually to try and avoid extremely large PCH files. The reason for this is that IncrediBuild needs to transfer the PCH file to every remote Agent participating in a distributed build. When PCH files are large, this can bec...
In certain cases, regular Visual Studio builds may perform better during the linking phase than builds executed with IncrediBuild. This is due to the way IncrediBuild generates and synchronizes multiple PDB and IDB files when exeecuting your build.  Bot...
Slow builds may be caused by AntiVirus software on your machine.   It is recommended that the Antivirus software will not be installed on IncrediBuild machines. However, if there is no way of avoiding the usage of Antivirus software, it is highly recomm...
The File Cache stores copies of all files transferred from remote machines, and should optimally be large enough to store the entire code tree (including standard header files). Additionally, persistent temporary files (like precompiled headers) and requi...
For the best build performance, it is recommended to disable the use of precompiled headers altogether. However if they are necessary, add the necessary precompiled headers to a single header file, such as "stdafx.h". If you intend on doing so, make sure ...
Help Desk Software by Kayako xoreax.helpserve.com