Re: performance enhancement by working copy svn server

"Ben Collins-Sussman" <sussman_at_red-bean.com> writes:

>So do we all. That's why we've always talked about making the 'svn
>edit' model into an *optional* mode of working. Try using subversion
>with a 700MB source tree; running 'svn status' takes minutes to crawl
>the tree (along with commits and updates).

No it doesn't, at least not with the WC on a decent local file system
and there is RAM to cache enough of it - it is usually a matter of
seconds or less once heated up. (I frequently develop on tmpfs because
of this, but ext3 works well too.)

But of course I agree, the current WC organisation scatters
information in lots and lots of files and directories and with very
expensive locking; there is a lot to gain by saner arrangements.

Of course, for those stuck with a slow file system (NTFS, UFS, NFS
etc), even a serious WC reorganisation may not help enough. This
remains to be seen - an 'svn edit' option would feel like admitting
defeat.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-10 19:31:45 CEST