RE: svn log "hangs"

Well that explains why it is *so* slow. The initial revision is from we
imported the repository and has thousands of files in the revision. Is
there a way to "kill" a revision? If I could somehow get rid of
that initial revision things might not be so bad...

However, I still don't understand why it has to check every file in the
revision. I understand why would would want to if your doing a "svn log
-v" which also reports all the files of each revision. But if your not
using the -v option then only information about that file is returned.
So why does it need to verify the paths for all the other files?

Ray

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Friday, November 05, 2004 12:07 PM
To: Ray Johnson
Cc: users@subversion.tigris.org
Subject: Re: svn log "hangs"

On Nov 4, 2004, at 8:17 PM, Ray Johnson wrote:

>
> Just to show I'm not exaggerating - I timed the "svn log" for a file:
> it took 5 minutes and 2 seconds.
>
> The file in question had only 9 revisions.

Sure, but if each of those revisions changed 300 files, then apache
needs to verify the readability of 2700 paths!

> Seems to me like some optimizations could be made in mod_dav_svn. For

> example, if the path doesn't change in any of the revisions why is the

> security constantly rechecked?

It's not the one file that's being re-checked. It's *every changed
path* in *every revision* returned by 'svn log' that's being checked for
readability.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 5 21:15:02 2004