I posted this question/issue on users@ and got a little bit of info from
Erik Huelsmann but wanted to see if I could get some more helpful
Basically I would like to be able to perform a partial tree update (svn
up -N [dir/file set]) with the same efficiency as a completely recursive
update. Currently, using a target list takes much longer (see below).
I'm willing to implement my own update procedure but after digging
through some docs I'm wary that I may be in over my head.
So - anyone have any ideas or pointers? Has this been done already?
Barring that, could I possibly call svn_ra_do_update with a custom
reporter that only returned info for my file set? Am I going down the
wrong path here?
Thanks for any info!
> -----Original Message-----
> From: Miller, Eric [mailto:Eric.Miller@amd.com]
> Sent: Tuesday, October 23, 2007 1:39 PM
> To: firstname.lastname@example.org
> Subject: Multi-path updates
> I just ran an interesting comparison of 2 raw svn update commands.
> update the nearly same set of data but the runtimes are drastically
> % time svn up
> 0.160u 0.320s 0:27.81 1.7% 0+0k 0+0io 1366pf+0w
> % time svn up -N * */*
> 31.440u 10.440s 14:38.91 4.7% 0+0k 0+0io 873409pf+0w
> The second run is a 32x increase in run time. Now my particular issue
> not quite the same as this (more to do with working around the lack of
> depth in the 1.4.x clients) but this seems seriously out of whack.
> My first thought is that svn_mucc solves a similar problem with
> copies/commits - is there anything around that does the same thing for
> - * */* expands to about 1100 paths, mostly sub-dirs with a few
> small files each
> - The first run actually updates more paths due to a few nested
> - The working copy was completely up to date, so no files were
> actually modified
> - Using svn+ssh:// (file:// sees a similar but not as drastic
> - svn 1.4.0
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Oct 24 17:25:06 2007