Remote Agent - Server Resource Consumption
I have a build that is very resource intensive. I’ve found that running this build alongside other builds can sometimes cause timeouts or false test failures. Because of this, I want to explore the option of running these resource hungry builds on a remote machine.
What kind of load does it put on the TeamCity server when running builds on an external machine/agent as opposed to running builds on one of the local agents?
Thanks
1 comment
Sort by
Date
Votes
Hi! Please be informed that running the build agents on separate machines from the TeamCity server machine is the recommended approach. When the agent is running on the separate machine, it doesn't create any addtional load on the server. Actually it is quite the opposite. The agent communicates with the server over HTTP(S) in both cases, and when the agent is running on a different machine, the server resource utilization is less. There can be a slowdown in the artifact publishing speed, if the agent is remote. If the agent needs to publish some large artifact files to the server, it may take longer compared to the transfer from the local agent.
Please sign in to leave a comment.