I am evaluating TeamCity and the same ant build took 30 minutes on the command line versus 2 hrs 18 mins in TeamCity. I used the same directory on the same machine for both builds. I did not do a clean or check any new source out of perforce. What could possibly cause this huge of a difference in build time? Any suggestions or ideas would be appreciated.

Votes

Share

Please check the timestamps of the messages in the build log (in the build results). Are there any particular steps that take longer then usual?

To be sure sources are not checked out and the time is not included in the overall build time, please use "Do not checkout files automatically" checkout mode (you will probably need to set "Build working directory" to the directory with the sources ready to be built.)

Please also make sure memory settings (like -Xmx) are the same for the manual and TeamCity builds.

TeamCity does introduce some overhead on grasping and sending build log messages to the server, etc. But it should be pretty much negligible.

If the slowness persists, could you please create a Jira ( http://www.jetbrains.net/jira/browse/TW ) issue and provide the following information?What is TeamCity version?What runner do you use? What are it's specific settings?What OS and platform do you use?If you can provide build agent and server logs ]]>/logs/teamcity-[agent|server].log and the build log itself that would also be of help.

I am going to go ahead and open a jira issue and include the logs and information you requested after the build finishes running tonight. It is one ant target that is particularly slow, but I can't figure out what could possibly make team city take 3+ times longer to complete than cruise control or running on the command line. Please let me know if you want me to include any other information.