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

Antwort: Re: TortoiseSVN not useable for large SVN projects

From: <Andreas.Otto_at_versit.de>
Date: Wed, 5 Nov 2008 11:41:29 +0100

Hi,

        thanks for the information ....

                but this is a "post morton" analysis ...

        I will not setup the whole repoisitory again just to make
TortoiseSVN working

        a few design steps will be usefull

                1. just skip the third window at all
                2. add a button saying something like show all or show
chunk for the guys need more information

        the commandline edition of svn does not have this problem ...

                        -> conclusion: it is not an SVN problem

                the problem is that the team of TortoiseSVN want to add
some nice eye candy ...

                        -> additional information for some users but a
blocker for the others

                conclusion -> TortoiseSVN should be fixed !!

        Question: who will do the job to fix this tool ?

 
Freundliche Grüße

Andreas Otto
ISV13 - Systemverantwortung Leben
 
Telefon 0431/603-2388
Sophienblatt 33
24114 Kiel
 
VersIT Versicherungs-Informatik GmbH
Gottlieb-Daimler-Str. 2, 68165 Mannheim
Registergericht: Mannheim HRB 6287
Vorsitzender der Geschäftsführung: Claus-Peter Gutt

Robert Graf-Waczenski <rgw_at_lsoft.com>
05.11.2008 11:13

An
users_at_subversion.tigris.org
Kopie

Thema
Re: TortoiseSVN not useable for large SVN projects

Hi,

when we started with svn (about two years ago) we already had a rather
large project (migrated from Visual SourceSafe). Before importing all
files into the repository, we already knew that importing all files in
one "big bang" would result in a huge revision with a gazillion of
files. So we separated the import into several chunks with a more
manageable size. The chunks were still considerably large and also take
more than a handful of seconds to display in TortoiseSVN, but we can
live with this.

The issue you observe now will diminish over time as your history
evolves. Future revisions will affect less files and TortoiseSVN by
default only scans the most recent 100 revisions, so your "big bang"
revision will be hidden then. (To gain access to older revisions in
TortoiseSVN, there is a button on the lower end of the screen saying
"Show All". And if i click on something like "Show All", a small delay
doesn't surprise me too much.)

Robert

Andreas.Otto_at_versit.de wrote:
>
> Hallo,
>
> I have a problem using TortoiseSVN on a large SVN Repository
>
> What is my problem:
>
> 1. I have imported the whole snapshot from an other system
> (Dimensions) to SVN
> 2. the Repository has a size of ~4G
> 3. all files were imported in one step
> 4. on windows I want to use the *Repo-browser*
>
>
>
> 5. using the* Show log* option to look into the history
>
>
>
>
> 6 opens a new window providing the log history able to do
> diffs between different revisions
>
>
>
> 7 the problem is the opening the *Log Messages* dialog is
> blocking the whole application for
>
> >>> ~1 minute <<<
>
> the reason is that in the 3 textarea from top all files were
> displayed
>
> >>> ~ 100000 files <<<
>
> which were in the same commit statement as this single file
>
> -> a whole repository scan is done
>
> this information is nice to to have for small repositories but
> a killer for large repositories special if
> modification (like a initial load) were done in one single step
>
> for me this information is totally useless and the blocking is
> unacceptable
>
> -> the maximum blocking timeout acceptable for me is
>
> >>> ~ 3 seconds <<<
>
> -> *what I can do to make the TortoiseSVN useable ?*
>
>
>
> mfg
>
> Andreas Otto

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-05 11:42:13 CET

This is an archived mail posted to the Subversion Users mailing list.

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