Build is slow in TeamCity

Symptoms

Builds are slow in TeamCity. In particular, they are slower than other alternatives, such as running it in a normal development environment or a different type of build step within TeamCity.

Troubleshooting

1. Check the build log to see if there are some long operations or the time is just spread over the entire process. You can compare build logs of slower and faster builds to figure out what the difference is.
   1. If the slowness is spread over all the operations, the agent machine resources (CPU, disk, memory, network) should be analyzed during the build to see if there is a bottleneck in any of those. If there is, the process loading the resource is to be found and investigated (e.g. with the help of the thread dump taken via "View thread dump" link on the running build results).
   2. If there is some long operation and it is a TeamCity-related one (before start or after end of the actual build process), the TeamCity agent and server are to be analyzed (logs and thread dumps).
2. You can also run the build from the console on the same machine as detailed in this article to see if there is any difference between the build run from the console and the build in TeamCity.

If you want to turn to us with the issue, please describe the visible effects, detail the process of investigation and attach the build log, full agent logs and other data collected.

More information

For general TeamCity server/UI slowness, see Slowness, Hangings and Low Performance.