Re: performance enhancement by working copy svn server

John Peacock <john.peacock_at_havurah-software.org> writes:

>I think that you underestimate the sheer scale of the performance drag caused by
>the existing WC code that will evaporate with centralized meta data *alone*.

Very true. For a rough estimate of the cost of the current WC
organisation, benchmark checkout/update/commit on an ordinary
(persistent) file system against tmpfs, where most operations are
extremely cheap[1]. A good WC design would attempt to minimise the
differences by using file system operations that are fast in both.

>The other thing that you are missing is that you (and I) are geeks, comfortable
>with a wide variety of sometimes cryptic commandline tools.

There are also rather sophisticated users who want their patch and
merge tools to work without having to be hacked to know about 'svn edit',
not to mention the other ad-hoc scripts and shell command lines we run
to change 4711 source files at the same time.

---
[1] So much cheaper, in fact, that I frequently use tmpfs for
    working copies despite the slight danger of losing recent
    changes in a kernel panic (which never happens anyway).
    With a better WC organisation, this wouldn't be necessary.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org