TeamCity Scalability

Many of the teams in our organization are moving towards implementing TeamCity as their release management system. The benefits and ease of use are incredible.

We think that we might get the most benefit out of all teams using the same server and increasing the number of agents (10-20). We will probably have 50+ users (just starting off) and our engineering organization and TC usage is only going to grow more. So, my question is, what type of scalability is documented for TC? What have others experienced? Would we be limited only by the capabilities of the AppServer TC lives behind? Is the bundled Tomcat sufficient? How well does the system scale with the number of users?

Also, from those who have had TC implemented for a while, could you offer some guidelines on how much space to plan for our TC database? We will be using oracle, but I'm just looking for rough numbers that will last me for quite a bit into the future, which I will then pad by probably about 25%.

Thanks for all of the anticipated help!

Ray

3 comments

Hello,

In Jetbrains we have our own TeamCity installation. Currently it has 50
agents. TeamCity server is installed on a PC with Pentium D CPU 3.2GHz and
4Gb RAM. PC is running under WindowsXP. On this PC we have TeamCity server
and MySQL server installed. We have 750Mb -Xmx configured for TeamCity
server, MySQL server uses about 500Mb. We have about 50 users working with
TeamCity everyday. So far the performance is ok.

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



"Ray Navarette" <ray_navarette@mapinfo.com> wrote in message
news:22532901.13291205846750525.JavaMail.jive@app4.labs.intellij.net...

Many of the teams in our organization are moving towards implementing
TeamCity as their release management system. The benefits and ease of use
are incredible.

>

We think that we might get the most benefit out of all teams using the
same server and increasing the number of agents (10-20). We will probably
have 50+ users (just starting off) and our engineering organization and TC
usage is only going to grow more. So, my question is, what type of
scalability is documented for TC? What have others experienced? Would we
be limited only by the capabilities of the AppServer TC lives behind? Is
the bundled Tomcat sufficient? How well does the system scale with the
number of users?

>

Also, from those who have had TC implemented for a while, could you offer
some guidelines on how much space to plan for our TC database? We will be
using oracle, but I'm just looking for rough numbers that will last me for
quite a bit into the future, which I will then pad by probably about 25%.

>

Thanks for all of the anticipated help!

>

Ray



0

Thanks for the quick reply. That info is what I was hoping to hear!

The 500Mb you mention for MySQL, I assume that is RAM. Could you offer any guidance on planning space for an Oracle database? Also, could you confirm that the Oracle database will run with Oracle 10g R2 (I believe this is what is mentioned in the JIRA for this issue).

Thanks again!
Ray

0

Ray Navarette wrote:

Thanks for the quick reply. That info is what I was hoping to hear!
The 500Mb you mention for MySQL, I assume that is RAM.

Could you offer any guidance on planning space for an Oracle database?
Also, could you confirm that the Oracle database will run with Oracle
10g R2
(I believe this is what is mentioned in the JIRA for this issue).

Internally We have hundreds of quite huge (IDEA, TC, Resharper) builds
with quite liberal cleanup policy and some builds in our history are
more than 2 years old.

MySQL ISAM takes slightly less than 2 gigs on HDD and half of this space
is used by passed/failed test data (typical build builds has 3 000 - 10
000 tests). Note that build artifacts are stored separately.

Database size is regulated by cleanup policy and is typically growing
during the day proportionally to number of builds done, than dropping
after cleanup. Median of this day cycle is relatively slowly growing due
to pinned builds and small amount of statistical data being accumulated.

After setting up new project (i.e. release branching) we usually notice
stable growth of DB size until reaching next plateau then new data is
balanced by its cleanup rules.

ORACLE integration and functional testing is done versus latest ORACLE
10g Express edition available.

--
Alexey Gopachenko
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0

Please sign in to leave a comment.