[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 17:35:06 CEST

On Sun, 2005-05-08 at 16:35 +0200, Thomas Zander wrote:
> I actually used https, since the update is reading I'm pointing this out as
> I'm not sure thats handled by dav..

It is. A lot of our working copy inefficiency is specific to the ra_dav
layer; you might try experimenting with the ra_svn layer (i.e. using
svnserve) and seeing how much that helps.

Of course, if you have other reasons to want to use http, it won't help
you very much to know that the network layer you don't want to use would
be much faster. But it would give us more evidence that we should be
fixing up the ra_dav layer as it relates to the workgin copy--either
using access batons, or (as I've argued we should in the past) ditching
the wcprops mechanism and synthesizing version-resource URLs instead of
remembering them. That gets into a complex argument about protocol
compatibility, but it's at least a relatively simply change to make.

If using ra_svn doesn't help enough, then more complicated changes might
be required, such as ones you suggested. (Although your particular
changes would break working copy severability, as has been noted
elsewhere in the thread. We might some day decide to sacrifice
severability for better performance, probably as part of a massive WC
library redesign, but right now it would be considered a bug.)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 8 17:36:13 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.