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

Re: Subversion is slow in big wc's (locking)

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2004-03-26 20:57:46 CET

Ben Collins-Sussman wrote:
> On Fri, 2004-03-26 at 13:47, Nicolás Lichtmaier wrote:
>
>>. Why does it
>>need to parse the "entries" file just to lock the directory?.
>
>
> You've got it backwards. The *main* activity is reading entries files,
> not locking directories.
>
> When you 'svn up', the client needs to report the local revision of
> *every* directory and file in your working copy to the server, just like
> CVS does. This means reading every single entries file in your tree.
> The locking stuff is just some extra protection, to make sure no other
> svn client changes the entries file on disk while the 'svn up' process
> is reading it.

Yeah, but he says he's doing an 'svn up Makefile', so why is it
recursing down the tree to read all the rest of the entry files?
Shouldn't it just read the top level one?

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 26 20:58:04 2004

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.