连接到 TFS 实例的最大 TFs 代理数
Maximum number of TFs agents connected to a TFS instance
在 Team Foundation (TFS2017) 上，您可以连接到 TFS 实例的构建代理的最大数量是多少？
这取决于代理服务器有多少核。一个Agent占一个核心。
目前没有任何官方文档说明TFS 构建代理数量的限制。也没有得到任何相关的提示信息如：build agents have reached the maximum.
对于多台机器，您可以根据需要进行配置，没有明显的限制。
对于单机来说，取决于硬件。如果您的代理服务器是虚拟的，那么它已经比物理服务器慢了，您还需要为其分配足够的内存。
Can I install multiple private agents on the same machine?
Yes. This approach can work well for agents that run jobs that don't
consume a lot of shared resources.
You might find that in other cases you don't gain much efficiency
by running multiple agents on the same machine. For example, it might
not be worthwhile for agents that run builds that consume a lot of
disk and I/O resources.
You might also run into problems if concurrent build processes are
using the same singleton tool deployment, such as NPM packages. For
example, one build might update a dependency while another build is in
the middle of using it, which could cause unreliable results and
errors.
在 Team Foundation (TFS2017) 上，您可以连接到 TFS 实例的构建代理的最大数量是多少？
这取决于代理服务器有多少核。一个Agent占一个核心。
目前没有任何官方文档说明TFS 构建代理数量的限制。也没有得到任何相关的提示信息如：build agents have reached the maximum.
对于多台机器，您可以根据需要进行配置，没有明显的限制。
对于单机来说，取决于硬件。如果您的代理服务器是虚拟的，那么它已经比物理服务器慢了，您还需要为其分配足够的内存。
Can I install multiple private agents on the same machine?
Yes. This approach can work well for agents that run jobs that don't consume a lot of shared resources.
You might find that in other cases you don't gain much efficiency by running multiple agents on the same machine. For example, it might not be worthwhile for agents that run builds that consume a lot of disk and I/O resources.
You might also run into problems if concurrent build processes are using the same singleton tool deployment, such as NPM packages. For example, one build might update a dependency while another build is in the middle of using it, which could cause unreliable results and errors.