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

Re: ideas to make svn update faster.

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-05-08 18:16:34 CEST

On Sun, 2005-05-08 at 18:00 +0200, Thomas Zander wrote:
> Do I understand correctly that the local filesystem access is different
> based on which network layer I choose?

Yes. The DeltaV protocol (which we sort of follow, but not very well)
requires us to use a server-provided "version-resource URL" for each
file and directory in the working copy. In practice, when talking to a
Subversion server, these URLs follow a very specific form, but in theory
they could be arbitrary. We have a mechanism called "wcprops" which we
use to cache these version-resource URLs in the working copy so that we
don't have to re-fetch them for each operation.

It has long been my position that we should give up on DeltaV (which is
a failed standard, in my opinion, and one that doesn't fit our
architecture) and consider ourselves to be talking a private versioning
protocol over HTTP/DAV. As part of that, we could feel free to
synthesize version-resource URLs, which would let us ditch the wcprops
mechanism, which would eliminate the discrepancy between ra_dav and
ra_svn in working copy performance.

Some developers agree with me and some don't; regardless, we haven't
gone in that direction as yet.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 8 18:17:32 2005

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.