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

Re: Performance of the log dialogue

From: Simon Large <simon_at_skirridsystems.co.uk>
Date: 2007-02-18 00:05:02 CET

Stefan Küng wrote:
> Auke Jilderda wrote:
>> I commonly use both TortoiseSVN and the command line client and
>> noticed that the difference in performance of the log sub command is
>> huge. For example, when requesting a server side log for some 7000
>> revisions (so no local WC involved, both clients running on the same
>> developer machine against the same server and repository on the
>> network, one log command right after the other), these were the times
>> needed for the log sub commands to complete:
>> tsvn: 11 minutes, 52 seconds
>> svn: 49 seconds (78 lines visible), 9 seconds (9 lines visible) (*)
>
> Now, do the same test again. But this time, don't do an
> svn log
> but an
> svn log -v
>
> because that's what TSVN is doing.
>
> I think the only way to speed up the log dialog is to not fetch the
> extended log but only the basic log. But that means the extended log
> needs to be fetched whenever the user clicks on a revision in the log
> dialog. Since that can get a little bit annoying because it slows down
> browsing, that would require an option in the settings dialog.

And also we have an issue open for caching log messages, which would
remove the delay almost completely. It's not finished yet, but a lot of
work has been done.

Stefan2, how's it going?

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Feb 18 00:05:02 2007

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.