Adriano Winter Bess wrote:
> I've been trying to use TortoiseSVN as a client of a (very) large SVN
> repository (around 20Gb with large directory tree) which consists
> mainly of binary files (CAD files from SolidWorks). The repository
> has just been imported and we don't have more than a couple of
> revisions (about 6, to be precise). By TortoiseSVN's side everything
> works fine, for the except of the Show Log function in the context
> menu. It takes *forever* - about 10 minutes or even more.
The svn:// access method is much faster than http://, but you're using
svn+ssh:// -- I don't know how this compares. You might try plain
svn:// just to see.
TortoiseSVN's Show Log is effectively doing a "svn log -v", which
includes all the path information of each revision. It sounds likely,
with a 20gb repository, that your initial import contains many many
files (and thus paths to list), so this would explain why Show Log is
slow even with only 6 revisions.
Particularly with the BerkleyDB database backend, a log -v operation
takes a large amount of CPU. Try running top on your server when you
run the Show Log command and see if you're maxing out the CPU.
If you are running BDB and your CPU is getting maxed, then try FSFS --
it is faster for these operations when the CPU is a limit. In any case
I've found that on a 100MB LAN the server CPU really is the bottleneck
so getting as fast as you can will help.
Subversion/TortoiseSVN 1.2 will have better limiting of how many logs
are initially shown. Once the number of revisions in your repository
goes over this limit (which you can configure, but defaults to 100,
IIRC) then for typical log operations you'll no longer have to wait for
the log -v on the first import revision, which should speed things up also.
HTH,
-Nathan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon May 16 18:31:21 2005