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

Re: [TSVN] Re: Log Messages dialog - slow fill

From: SteveKing <steveking_at_gmx.ch>
Date: 2004-09-13 18:10:40 CEST

Paul De Velder wrote:

>>The size of the repository doesn't matter. But the number of revisions
>>you get the log for does. (And of course how fast your computer is...)
>
> Stefan, I have my doubts about this. My repository contains only 3 revision :
> the initial import of a part our VSS repository (+8000 files) and 2 revisions
> containing less than 100 files that changed. I cannot believe that these 3
> revisions are the reason why this Log Messages dialog box fills so slowly. When
> I use the svn shell I get my response immediatly.

Ok, I see where the problem is:
If the list of changed files per revision is really big like with an
initial import, it takes some time to fill the dialog. That's because
memory has to be allocated for the list.
But: usual commits only affect a few files, so showing the log isn't a
problem in those cases.
If you don't want to show the import revisions in the log, you can set
the amount of log messages should be fetched the first time in the
settings dialog - default is 100. Reduce that number, and you won't get
down to revision 1 from your initial import. Then, once you have some
more commits in that repository and therefore a higher HEAD revision,
you can increase that value again.

> I have the impression that Log Messages dialog buffers all the info it needs
> before the ondraw : so it does 1 x 'snv log' and revision x 'svn list'.

Only partly true: yes, the dialog buffers all the info it needs. But it
fetches the information in one step - the svn_client_log() function
returns everything there is, no need for an additional 'svn list'. Just
try the command 'svn log -v' and you'll get the same...

> With my suggestion I would avoid those revision x 'svn list' before showing
> the results. When one wants to see all the files that were changed in a given
> revision, only 1 'svn list' explicitly needs to executed. Since you don't need
> to retrieve the info on all the files that were changed in all the revisions,
> it will be faster.

One thing you should think of: there are many, many projects out there
which are not accessible via LAN but slow internet connections. So I
will do whatever I can to reduce the number of connections made to a
repository - even if it might be better in your case.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Sep 13 19:13:52 2004

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