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

Re: [TSVN] TSVN vs SVN Performance Issue

From: Simon Large <slarge_at_slarge.plus.com>
Date: 2005-06-07 16:05:10 CEST

jwhitby@bankofny.com wrote:
> I have a FSFS repository with 127 revisions in it with 1800 files
> under version control.
> The repository resides on a network share.
> The working copy resides on a network share.
> The working copy is accessed via a subst drive letter.
> All access is via File:
>
> Using TortoiseSVN ver 1.2.0 Build 3614
> required 660,000 file accesses with all but 31,621 of these file
> accesses being to file Repository\db\revs\1.
>
> Using SVN version 1.2.0.
> process has required 28,250 file accesses.
>
> So to cut to the chase:
> 1) are these commands equivalent?

No. You will notice that TSVN's ShowLog gives you the list of changed
files with each revision. The command line equivalent is therefore:
svn log -v absolute/path/to/a.txt

I guess there was a huge import at rev 1 and the extra activity is due
to fetching all those paths.

I do not know a lot about networks, but my guess is that you would get
better results by using a server (svnserve is small and simple) rather
than file:// access over the network. That way, only the output gets
sent over the network instead of letting Windows send all those file
open/seek/read requests over the network.

You would also benefit from keeping your working copy on the local hard
disk, although it won't help in this case.

Simon

-- 
       ___
  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 Tue Jun 7 16:06:56 2005

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.