Slow StarTeam communications

Avatar
Rick Cole
Created

We are experiencing some issues with our connectivity to StarTeam. We have two StarTeam servers: one local and one remote. The local server seems "fine", in that performance seems acceptable. However, the remote server seems inordinately slow. Here is a sample from our log:

: Checking for changes
: Building in C:\buildtools\BuildAgent\work\e2c1bff6301391fc
: Clearing temporary directory: C:\buildtools\BuildAgent\temp\buildTmp
: Clean build enabled: removing old files
: Getting project sources
: Loading changed files from server...
: Updating C:\buildtools\BuildAgent\work\e2c1bff6301391fc
: Clean directory C:\buildtools\BuildAgent\work\e2c1bff6301391fc
: Updating C:\buildtools\BuildAgent\work\e2c1bff6301391fc\Development\upgrade
: MAVEN_OPTS = -mx1024m "-Dteamcity.buildConfName=Upgrade Build (HEAD)"

As you can see, the 'Checking for changes' step seems to be taking a very long time. In fact, there have been times this step just sat there for hours at a time. I can run the StarTeam client from this same machine and checkout the same code in about 5 seconds. This project only has about 300k of data. What do each of these steps do? We are setup for a clean before we build so I assume that TeamCity is not doing a compare on each file. I have turned up the logging for both vcs and StarTeam on TeamCity and I don't see anything unusual (timeouts, etc...) What could be happening during this step?

Rick Cole
PitneyBowes Software, Inc.

Votes

0

Share

1 comment
Avatar
Permanently deleted user
Created

Hello Rick,

Please send me teamcity-starteam.log located in the /logs directory. Specifically I need to see the records corresponding to one of your typical builds. Also ensure /conf/teamcity-server-log4j.xml contains the following fragment ]]>
<param name="file" value="$teamcity-starteam.log"/>

]]>
<param name="ConversionPattern" value="[%d] %6p - %30.30c - %m
%n"/>
</layout>
</appender>

Note that layout params are important. The default configuration differs
from the one above.


Thank you.

We are experiencing some issues with our connectivity to StarTeam. We
have two StarTeam servers: one local and one remote. The local server
seems "fine", in that performance seems acceptable. However, the
remote server seems inordinately slow. Here is a sample from our log:

: Checking for changes
: Building in C:\buildtools\BuildAgent\work\e2c1bff6301391fc
: Clearing temporary directory:
C:\buildtools\BuildAgent\temp\buildTmp
: Clean build enabled: removing old files
: Getting project sources
: Loading changed files from server...
: Updating C:\buildtools\BuildAgent\work\e2c1bff6301391fc
: Clean directory
C:\buildtools\BuildAgent\work\e2c1bff6301391fc
: Updating
C:\buildtools\BuildAgent\work\e2c1bff6301391fc\Development\upgrade
: MAVEN_OPTS = -mx1024m "-Dteamcity.buildConfName=Upgrade
Build (HEAD)"
As you can see, the 'Checking for changes' step seems to be taking a
very long time. In fact, there have been times this step just sat
there for hours at a time. I can run the StarTeam client from this
same machine and checkout the same code in about 5 seconds. This
project only has about 300k of data. What do each of these steps do?
We are setup for a clean before we build so I assume that TeamCity is
not doing a compare on each file. I have turned up the logging for
both vcs and StarTeam on TeamCity and I don't see anything unusual
(timeouts, etc...) What could be happening during this step?

Rick Cole
PitneyBowes Software, Inc.

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Please sign in to leave a comment.