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

Re: Quick analysis of svn log --limit

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2005-05-08 18:43:05 CEST

D.J. Heap wrote:
> I'm not terribly familiar with the code in libsvn_repos, but there are
> two places that seem to be the source of slowness even with --limit
> turned on:
> subversion/libsvn_repos/log.c:svn_repos_get_logs3 -
> 1. When passing one path such as /trunk (or / which mod_dav_svn
> always seems to do even if no deeper path was specified) it performs the
> svn_repos_history2 call and spends a lot of time there gathering all
> revs for the path (which is nearly all the revs in the repo for /trunk
> and *is* all revs in the repo for /). So, svn_repos_history needs to be
> revved to take a limit parameter?

That seems likely to fix the problem, or if we don't want to rev
svn_repos_history2 (perhaps so that such a change could be merged into a
subsequent 1.2.x release) we could also change svn_repos_get_logs3 to
call svn_repos_history2 iteratively with progressively further back
ranges of revisions until it finds enough revisions to satisfy the limit


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 8 18:43:50 2005

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.