On Wed, 2008-09-03 at 03:16 -0500, Ryan Schmidt wrote:
> On Sep 2, 2008, at 1:25 AM, N D wrote:
>
> > On Mon, Sep 1, 2008 at 4:04 PM, Esben Nielsen wrote:
> >
> >> We have set up subversion and CruiseControl. Whenever CruiseControl
> >> checks for changes on the subversion with "svn log -v -r{timestamps}"
> >> the operation itself takes a very long time AND every other
> >> concurrent
> >> operation, like browsing the reporsitory from Eclipse, takes a
> >> very long
> >> time.
> >>
> >> When CruiseControl is not doing "svn log" everything is fairly
> >> responsive.
> >>
> >> But top shows no CPU nor much IO usage. What makes subversion so
> >> slow?
> >>
> >> CruiseControl is running on the same host as subversion but using
> >> svn://
> >> Subversion version is 1.5.1 and OS is Fedora 8 x86_64.
> >
> > I have a similar experience. When I do a svn log -v, no arguments
> > would mean it would log changes on the WC, it runs very slow.
>
> I think I remember something about the log getting slow if the
> requested revision range contains a revision that touches *many*
> files or directories. Do you have a revision in which you imported
> hundreds or thousands of files at once, maybe to import a large
> existing project?
>
As CruiseControl checks for changes since last build (based on
timestamps), that problem might occur once someone have checked in a lot
of files; but as soon as CruiseControl have build the system and
thereafter starts asking for the log since a later timestamp, the
problem should go away.
Esben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-03 16:31:24 CEST