RSS Feed
Knowledgebase : Performance
The following hardware characteristics have a significant impact on the performance of IncrediBuild Agents (in order of significance): 1. Number of CPUs/cores: multiple CPUs or cores allow IncrediBuild Agents to utilize each core in parallel to execut...
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...
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...
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 best build performance, either disable use of PCH altogether, or use precompiled headers through a single header file (like stdafx.h). If you choose the second option, invest time in adding #include statements for header files that are commonly used b...
Help Desk Software by Kayako xoreax.helpserve.com