Checking for Changes and Getting Sources Takes a Long Time

I'm using CVS and the amount of time spent checking for changes and getting sources seems much longer than I'd expect, given similar runs for the same repositories using the command line cvs.

Is there anything that can be done to tune this? Speed it up? Known issues with check speed?

--Tim

9 comments
Comment actions Permalink

Hello Tim,
Do you have 'history supported' option enabled?

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


"Tim McNerney" <intellij@oneofus.org> wrote in message
news:22697866.1177178507293.JavaMail.itn@is.intellij.net...

I'm using CVS and the amount of time spent checking for changes and
getting sources seems much longer than I'd expect, given similar runs for
the same repositories using the command line cvs.

>

Is there anything that can be done to tune this? Speed it up? Known issues
with check speed?

>

--Tim



0
Comment actions Permalink

I do not have "History command supported" enabled. The only of the Advanced Options I have set is "Use GZIP compression".

--Tim

0
Comment actions Permalink

Does enabling "History command supported" speed things or slow things?

--Tim

0
Comment actions Permalink

Speeds (at least it should)

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


"Tim McNerney" <intellij@oneofus.org> wrote in message
news:23055613.1177434941085.JavaMail.itn@is.intellij.net...

Does enabling "History command supported" speed things or slow things?

>

--Tim



0
Comment actions Permalink

It should speed things :)

0
Comment actions Permalink

Enabling "History command support" seems to speed things up dramatically, but it still seems very slow.

In one specific example, it was taking 41 minutes to check sources and 16 minutes to get them. After enabling History command support, it took 24 and 7 minutes respectively.

What are the specific cvs commands that are run for the two cases?

--Tim

0
Comment actions Permalink

In both cases rlog is being used, but if history not supported we run rlog
for the whole project, otherwise we run rlog only for changed files (which
ones were changed we're discovering from 'history' command output)
.

How long does it take to call history for your project?
We run
cvs history -a -x AMR -p $ -D ${date in yyyy/MM/dd HH:mm:ss ZZZZ
format}.

Thanks!
--
Olesya Smirnova
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


"Tim McNerney" <intellij@oneofus.org> wrote in message
news:27201200.1177447579847.JavaMail.itn@is.intellij.net...

Enabling "History command support" seems to speed things up dramatically,
but it still seems very slow.

>

In one specific example, it was taking 41 minutes to check sources and 16
minutes to get them. After enabling History command support, it took 24
and 7 minutes respectively.

>

What are the specific cvs commands that are run for the two cases?

>

--Tim




0
Comment actions Permalink

It takes a couple of minutes.

I think I've figured out another (the main) problem. We have more than a dozen CVS roots in one project and I think that may be slowing things down (overhead for each CVS call). We have cvs aliases which has helped in the one project I checked. We didn't use them at first, because in a very early beta version of TeamCity, I was unable to get directories to line up correctly. I think it will work now and will try with some additional projects to see if things are better.

--Tim

0
Comment actions Permalink

Things seem to be going much more quickly in terms of updating, but now the changes are no longer being picked up. At least, they aren't being listed. None of the builds show changes any more, though a lot have been put in. When I reverted to using individual modules, things seemed to work again.

Is there a known limitation when working with CVS aliases?

I'll open up an issue when I have more details.

--Tim

0

Please sign in to leave a comment.