When our project is at the "Getting project sources" stage of the build process, it seems TeamCity is taking an excessive amount of time to pull the source. Looking at the agent, it is barely using any CPU, memory, or hdd access during the stage, so it hardly seems like it is actually checking out the source. Even in a stripped down build configuration, it can take up to 40 minutes to pull the source before it will even move on to looking for changed files. In comparison, I can pull the full source directory on my system using Visual Studio 2005 in about 5 minutes or so, and our previous CC.NET system performed about the same in 5-7 minutes.
We are using Team Foundation Server 2005 for source control, and the build agents are set to read from an MSBuild file for instructions. The problem with "getting project sources" occurs before it even gets to the MSBuild file, so I'm not worried with what it is doing.
Our current testing configuration for TeamCity consists of TC 4.0 EAP server on a dedicated dual-core system with 4gb ram, and a corresponding 4.0 EAP agent on a dedicated dual-core system with 2gb ram. Both run Windows XP Professional with a minimum of unrelated system services.
I've seen this issue on different systems in TeamCity 2.1, 3.0, 3.1, 3.1.1, and now 4.0, so I wanted to reach out and see if anyone had suggestions. Is anyone else seeing frustratingly slow source pulls? If you did, what did you do to fix it?