Slow integration under 64bits Windows 2003 (minutes vs seconds)

Hi,

We have installed TeamCity 3.0 EAP in two machines. One machine has Windows Server 2003 32-bits version, and the other one has Windows Server 2003 64-bits version.

Compiling and executing a small suite of unit tests takes about 23 seconds under the 32 bits version machine, compared to almost 90 seconds on the 64 bits machine (with the same projet and same build configuration).

Is it possible that Team City (maybe the JVM) is better optimized for 32 bits than 64 bits Windows 2003 Server OS? We'd have no problem changing our OS. Right now we're in the state of investigation.

Thanks for your help!

Brian

5 comments

Hello Brian,

What build-runner do you use? What tests do you run? (.NET or JAVA), What
unit test runner is used?

How was TeamCity Build Agent installed to 64-bit machine? Do you use 64-bit
JVM?

--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi,

We have installed TeamCity 3.0 EAP in two machines. One machine has
Windows Server 2003 32-bits version, and the other one has Windows
Server 2003 64-bits version.

Compiling and executing a small suite of unit tests takes about 23
seconds under the 32 bits version machine, compared to almost 90
seconds on the 64 bits machine (with the same projet and same build
configuration).

Is it possible that Team City (maybe the JVM) is better optimized for
32 bits than 64 bits Windows 2003 Server OS? We'd have no problem
changing our OS. Right now we're in the state of investigation.

Thanks for your help!

Brian



0

1. What build-runner do you use? => SLN2005

2. What tests do you run? (.NET or JAVA) ==> .NET

3. What unit test runner is used? ==> NUnitTeamCity

4. How was TeamCity Build Agent installed to 64-bit machine? ==> We downloaded the installer file from http://download.jetbrains.com/teamcity/TeamCity-5725.exe and installed it directly to the machine. Everything was successful and running.

5. Do you use 64-bit JVM? ==> No we are not. We installed the OS (64 bit Windows 2003 Server), IIS 6.0, .NET 2.0 and then Team City. The only Java "soul" in the machine is the one provided by TeamCity's JRE.

Thanks for your help Eugene, it is very much appreciated,

Brian

0

Hello Brian,

To tell the truth, TeamCity agent installer is unable to run BuildAgent as
service under
64-bit windows running 64-bin JVM. If you want to use 64-bit JVM you will
have to install it and that start buildAgent using agent.bat
(from ]]>/bin). Make sure to set up JRE_HOME environment variable
to point to newly installed Java.
Thus it starts 32-bin java process which running the build and starting .NET
processes
of MSBuild and tests runner.

Do you use .NET Framework 64-bit?

What time will it take to run build from console? (Please make sure to use
64-bit .NET)

Do you have TeamCity server on 64-bit-OS machine?
--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

1. What build-runner do you use? => SLN2005

2. What tests do you run? (.NET or JAVA) ==> .NET

3. What unit test runner is used? ==> NUnitTeamCity

4. How was TeamCity Build Agent installed to 64-bit machine? ==> *We
downloaded the installer file from
http://download.jetbrains.com/teamcity/TeamCity-5725.exe and installed
it directly to the machine. Everything was successful and
running.*

5. Do you use 64-bit JVM? ==> *No we are not. We installed the OS
(64 bit Windows 2003 Server), IIS 6.0, .NET 2.0 and then Team City.
The only Java "soul" in the machine is the one provided by TeamCity's
JRE.*

Thanks for your help Eugene, it is very much appreciated,

Brian



0

Hi Eugene,

We are using and targeting the .NET 64 bit version on the system. We do have TeamCity server on the 64 bit-OS machine.

What I'll try is installing the 64-bit JVM and change the JRE_HOME variable to point to it.

TeamCity runs fine under the 64-bit machine, is just that the build takes over a minute to run (my guess is the missig JVM 64-bit, because it compiles and runs the unit tests just fine, it's just that it's way too slow for us).

I'll try the JVM 64-bit right now. If I still get performance issues, I'll just revert to a 32-bit OS since we don't need the 64-bit platform for our projects.

Thanks Eugene :)

0

Hello Brian,

Ok. Just curious if to start the build on that machine without using TeamCity
what would be the execution time?
So the idea is to figure out if the perfomance slows down because of TeamCity
build agent, or not.

Thanks!

--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hi Eugene,

We are using and targeting the .NET 64 bit version on the system. We
do have TeamCity server on the 64 bit-OS machine.

What I'll try is installing the 64-bit JVM and change the JRE_HOME
variable to point to it.

TeamCity runs fine under the 64-bit machine, is just that the build
takes over a minute to run (my guess is the missig JVM 64-bit, because
it compiles and runs the unit tests just fine, it's just that it's way
too slow for us).

I'll try the JVM 64-bit right now. If I still get performance issues,
I'll just revert to a 32-bit OS since we don't need the 64-bit
platform for our projects.

Thanks Eugene :)



0

Please sign in to leave a comment.