Ben Collins-Sussman <sussman@collab.net> wrote:
>> So it appears to be just very slow. I let it go and this is the
>> result:
>>
>> real 6m9.907s
>> user 0m1.683s
>> sys 0m0.825s
>>
>> 6 minutes is really a long time and SVN absolutely provides *no*
>> feedback at all during 99% of this time.
>
> That's because update and switch commands walk over the working copy
> and report revisions/paths to the server. In your pathological case, the
> client must report *every* object in your tree to the server. That's
> what's taking so long.
I see.
Do you believe that the fact that an aborted 'svn switch' left me in this
pathological case might be an issue, then? After all, I just hit CTRL+C while
'svn switch' was running, which looks like a legitimate thing to do. I'm afraid
I can provide more details about this because weeks are passed by since this
happened.
> Still, it would be interesting for
> you do to a completely new 'svn checkout' of the branch, and then time
> how long it takes to 'svn up' the working copy.
$ svn co http://svn.collab.net/repos/svn/branches/1.2.x subtest
[...]
A subtest/svn-config.in
U subtest
Checked out revision 14899.
$ cd subtest
$ time svn up
At revision 14899.
real 0m2.558s
user 0m0.092s
sys 0m0.034s
It looks reasonable to me. I also tried to switch to the trunk and back:
$ time svn switch http://svn.collab.net/repos/svn/trunk
[...]
Updated to revision 14899.
real 0m18.696s
user 0m1.357s
sys 0m1.023s
$ time svn switch http://svn.collab.net/repos/svn/branches/1.2.x
[...]
Updated to revision 14899.
real 0m16.687s
user 0m1.355s
sys 0m0.929s
$ time svn up
At revision 14899.
real 0m1.326s
user 0m0.094s
sys 0m0.037s
Giovanni Bajo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 1 05:00:52 2005