Re: TSVN update much slower than "svn update"

On 04.09.2009 22:19, Purple Streak wrote:
> 2009/9/4 Stefan Küng<tortoisesvn_at_gmail.com>:
>> On 04.09.2009 17:42, Purple Streak wrote:
>>> 2009/8/12 Purple Streak<mrpurplestreak_at_googlemail.com>:
>>>> 2009/8/2 Stefan Küng<tortoisesvn_at_gmail.com>:
>>>> Hi - just got back to looking at this again. Switching to serf does
>>>> make a big difference. However serf seems to make the command line
>>>> slower (and my perception is that TSVN is still slower then it used to
>>>> be and slower that it is for my collegues). For a simple svn list it
>>>> almost doubles from 0.3s to 0.6s. Not that this is a lot, but when
>>>> my TSVN was fast then it made the repo browser so much more
>>>> responsive. Over a largeish checkout serf takes 3m41s, neon takes
>>>> 2m43s
>>>>
>>>> You also said:
>>>>>>> The command line client doesn't have SSPI compiled in,
>>>>>>> so it won't have an issue with that at all.
>>>>
>>>> From what i've looked at the command line uses neon to do SSPI. If I
>>>> tunnel the connection through a proxy the command line seems to be
>>>> using only NTLM auth, and never asks me for a password (despite having
>>>> cleared my auth cache) where as TSVN does sometimes ask for this.
>>>> Does TSVN have it's own SSPI code in somewhere? Otherwise I can't see
>>>> why it would work fine for the command line but not for TSVN?
>>>
>>> Hi - Sorry to bump this but I'm still stuck looking for where this
>>> would be different in TSVN (see my previous query about)? I've got a
>>> debug tortoise built, so if you could point me at the bit where
>>> tortoise does the SSPI then I can try and debug what is happening.
>>
>> If TSVN asks for authentication only sometimes, it's usually because the
>> diff to transfer is too big (maybe that's why you haven't seen this with
>> the CL client, you might have not done the same big commits/updates/...
>> as with TSVN).
>> See here:
>> http://svn.haxx.se/tsvnusers/archive-2008-02/0329.shtml
>
> We do have that, but this is a different issue :) This is more the
> initial connection takes a while, e.g. on update. So once an update is
> running it's fine, but each time it takes a while to connect. Just to
> refresh on the initial post
>
> I seem to have an odd issue with my (and just my) tortoise SVN.
> If I run an svn udpate from the command line in my working copy
> it takes ~3 secs to complete. If I run it from tortoise it takes
> 45 seconds.
>
> The main issue is that it has 4 or 5 externals to check, and so the
> connection for each of them takes time. So if I knew where TSVN
> differs from the command line then it might give me a starting point
> to look at why.

TSVN uses the very same libraries as the CL client.
But there's one difference between UI and console apps: virus scanners
and 'firewalls' treat those differently. While console apps are usually
left alone, UI apps are not. It could very well be that your virus
scanner interferes with the SSPI authentication of TSVN but leaves the
console client alone.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2392606
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].