How can we ensure more powerful agents will run builds first?

For our TeamCity agents, we have dedicated hardware servers, and we have EC2 cloud agents. We noticed that sometimes even though the more powerful physical machines are available, with a higher CPU ranking on the agent page, a build is launched on an EC2 agent. The Ec2 agents run the builds and tests in a longer time than the EC2 agents. How can we ensure that the builds will always start on the faster, hardware servers? It seems that the CPU number is disregarded.

Please sign in to leave a comment.