On Tue, 26 Apr 2005, Eric Gorr wrote:
> Ludvig Strigeus wrote:
> > If I run "svn status" in a repo with 3200 files, SVN does 310000 file
> > operations such as open/read/close/stat.
> >
> > It looks like it's comparing the contents of EACH file with the base/
> > file. That's overkill. It reads hundreds of megabytes from the disk for
> > no real reason.
>
> A performance improvement that may be in there (is it?) for 1.2 would
> also seem to be checked to see if a file (hopefully I get this right)
> needs to be locked before being modified. If this is the case and it
> was not locked, there would not seem to be a need for svn status to
> check further.
>
Nope. It doesn't work that way. svn:needs-lock can be cicumvented by
tools. If we didn't check the actual file, we could overwrite user
changes, which is not very popular.
> The way I would intend to use 1.2 would be to set the needs-lock flag
> for every file.
If your only motiation for that is performance, then don't bother:-)
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 26 15:27:03 2005