[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Really lousy performance with svn info --depth infinity

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Thu, 01 Sep 2011 17:00:35 +0100

"Bert Huijben" <bert_at_qqmail.nl> writes:

> These operations do very different things. The first reads your
> working copy to obtain a lot of details (unless you pass a revision;
> in that case it looks at the repository)
> The second asks the repository what files there are below the current
> directory in the repository (using the revision of the current
> directory).

Both commands access the working copy to read the info for every file
and directory.

> In my usage (repository hosted via http:// on the other side of the
> world) the second is much slower. But if you have a local repository
> the opposite might be true.
> I think this question belongs on users{_AT_}subversion.apache.org
> though, as it is about using Subversion and not on Subversion
> development.

I disagree. Since both commands pull all the info from the working copy
it is a problem if the single recursive call is slower than multiple
non-recursive calls. If this is reproducible then we want to know why,
however I cannot reproduce it on my machine.

> From: michael_rytting_at_agilent.com [mailto:michael_rytting_at_agilent.com]
> Sent: donderdag 1 september 2011 17:26 To: dev_at_subversion.apache.org
> Subject: Really lousy performance with svn info --depth infinity
> Quick question. I would expect the following 2 commands to perform
> equivalent functions.
> svn info -depth infinity
> svn ls -depth infinity | xargs svn info
> This issue is that the first command takes 1 minute to run while the
> second command takes 6 seconds to run. I am running 1.7.0-rc2.

uberSVN: Apache Subversion Made Easy
Received on 2011-09-01 18:01:10 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.