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

Re: Optimizing SVN switch

From: Bill Soudan <bill_at_soudan.net>
Date: 2004-04-09 21:19:47 CEST

On Fri, 9 Apr 2004, C. Michael Pilato wrote:

> Bill Soudan <bill@soudan.net> writes:
> > For now, I'll switch over to svnserve. What should I do from here? File
> > an enhancement request for ra_dav? Or is this dramatic enough to be
> > considered a bug?
> Is the problem that we use wcprops stored separately, or is 'svn
> switch' over ra-dav still sending the giant "resource walk" at the end
> of the switch REPORT response (which writes every wc-prop in the whole
> tree) ?

From my original mail:

> stracing the svn client reveals the following points of note:
> 0.0000s - some sort of wc check
> 0.1682s - tree lock, read entries files
> 3.5427s - open .svn/tmp/tempfile.tmp
> 3.5448s - scan wc directories, getdents64
> 5.7612s - contact repository over socket, do stuff
> 5.9175s - read wcprops for each file & dir & then set to 'END'
> 141.????s - do actual wc updates
> 143.1844s - read wcprops for each file & dir & then set to new value
> 267.9598s - write new entries files
> 275.6327s - close & rm .svn/tmp/tempfile.tmp, unlock tree
> 277.2784s - operation complete

I don't know much about the SVN internals yet but it looks like there's
two 'resource walks' here, one where it removes all the wcprops (thus
wrinig END to each file) which takes ~136s and then the second where it
sets the updated key/value which takes ~124s.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 9 21:20:15 2004

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.