On Thu, 19 Jan 2006, Dave Rodgman wrote:
> > > Also, it seems that this affects other svn commands, including ls,
> > > plist, info, co.
> > >
> > This makes me suspect that this is caused by the history-following peg
> > revision support, at least if you have 100k's of revisions. If so, 1.3.0
> > should help, since the history-following algorithm was improved in this
> > release.
>
> The following timings are against a 7k commit repository (FSFS again) -
> I'm afraid 1.3.0 isn't significantly better.
>
> $ time subversion-1_0_5/Linux-redhat-7_2-i686/bin/svn ls
> http://cam-svn1/svn/devsys/testing -r 3000
> admin/
> current/
> testUpdate/
> testharness/
>
> real 0m1.030s
> user 0m0.020s
> sys 0m0.000s
>
> $ subversion-1_2_0/Linux-redhat-7_2-i686/bin/svn ls
> http://cam-svn1/svn/devsys/testing -r 3000
> admin/
> current/
> testUpdate/
> testharness/
>
> real 1m18.013s
> user 0m0.020s
> sys 0m0.010s
>
Yeah, history tracing was introduced in svn 1.1.
> $ time subversion/1.3.0/1/linux-redhat_7.1-x86/bin/svn ls
> http://cam-svn1/svn/devsys/testing -r 3000
> admin/
> current/
> testUpdate/
> testharness/
>
> real 1m11.279s
> user 0m0.000s
> sys 0m0.000s
>
But this was using the same server, I guess. Which version runs the
server? The 1.3 improvement is on the server side.
Thanks,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 19 13:30:32 2006