Multiple agents per box?

Does it make sense / is it possible to install multiple agents to one single box? In our case, we have a dual quad core as a build server. I would like to assign more than one task at a time to this build server. Is this possible / reasonable?

6 comments
Comment actions Permalink

It is possible. For this you should manually choose different ownPort and name for these agents in <build agent dist>/conf/buildAgent.properties file.

If your builds take significant time and eat CPU be prepared to see some slowdowns on the server side (if these agents are installed on the same box where TeamCity server is installed) and increased build durations.

0
Comment actions Permalink

So you recommend not to install multiple agents on the TeamCity server box? This would be our use case since the dual quad core is in fact a different box.

How many agents would you recommend for such a box? 8? Less than 8? Why?

0
Comment actions Permalink

I can't give you concrete recomendation because I do not know what kind of builds do you plan to run on these agents. You can try to install two agents and see whether performance is acceptable for you. If performance is ok, you can add more agents and so on.

However there is one more thing you definitely should be aware of. Build can do anything on the agent box, it can even remove all files from disk. It all depends on how build scripts are written and what are the permissions of the user under which agent is running. Probably it is simpler to use vmware or something similar. BTW in our own grid we are using virtual agents too.

0
Comment actions Permalink

Probably it is simpler to use vmware or something similar. BTW in our own grid we are using virtual agents too.


"Virtual agents" are those which run on virtual machines? But I suppose vmware to be a serious performance issue, especially when there are multiple machines on a single physical box, isn't it?

0
Comment actions Permalink

One on of our PC we have three virtual agents. Of course, there is slowdown, but in our case it is acceptable.

0
Comment actions Permalink

Sounds acceptable to have various different test platforms on one single box. In our case, we try to build up more build capacity to shorten our turnaround times.

But at the moment, those builds run on one single dual core server as well, just somtimes there are 8 or even more of them at the same time, which slows down the build process drastically.

I'll go for the "add one after one and observe the performance impact" way, I guess. Thanks anyway.

0

Please sign in to leave a comment.