Hello,
when I was testing svn 1.2.0 I found, that svn log -v is much slower compared to
the same command in svn 1.1.4, if its used on a repository containing revisions
with a large number of changed paths.
If this is related to the revisions r14116+r14722+r14759, which are mentioned in
the releasenotes for svn 1.2.0, then ignore the rest of the mail ;) .
Otherwise here are my test specs:
command:
svn log -v >/dev/null
Subversion Packages:
svn-win32-1.2.0.zip,
svn-win32-1.1.4.zip
Repository:
fs type: fsfs
db size:
736 mb
27000 files
9000 directories
9 revisions
5 revisions with >20000 changed paths
OS:
WindowsXP SP2
Web-Server:
Apache_2.0.54-win32-x86-no_ssl
(with SVNPathAuthz off)
And here the test results:
Access method file:///
Version Duration
1.1.4 5.1s
1.2.0 133.5s
Access method svn://
Server Version 1.1.4
Client Version Duration
1.1.4 5.4s
1.2.0 5.5s
Server Version 1.2.0
Client Version Duration
1.1.4: 135.1s
1.2.0: 138.5s
Access method http://
Server Version 1.1.4
Client Version Duration
1.1.4 5.6s
1.2.0 5.7s
Server Version 1.2.0
Client Version Duration
1.1.4: 141.1s
1.2.0: 140.9s
Svn log without the -v option is still fast, but the log dialog of TortoiseSVN
is calling the svn api in the same way as svn log -v does.
So TortoiseSVN is just unusable, if my test repository is hosted by a svn 1.2.0
server.
Is there a way to accelerate svn log -v in 1.2.0?
Ronny
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 7 18:48:36 2005