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

Re: SVN merge issue in Solaris

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Wed, 26 May 2010 22:56:31 +0200

On Wed, May 26, 2010 at 9:20 PM, Liu, Xiaodu "Louie"
<XiaoduLouie.Liu_at_westernasset.com> wrote:
> We have the svn merge performance issue on Solaris.  For a given repo, if
> we do svn merge on windows box, it takes about 35 seconds, but same merge
> will take about 6 minutes.
>
> Both svn version 1.6.6 and 1.6.11 clients are tested with the same issues.

There could be lots of differences between both (client) systems. If
network connectivity to the repository is the same, I would take a
look at the filesystem where the working copy is stored (where you are
merging into). For instance, if your working copy on the Solaris box
is on a remote filesystem mounted via NFS, or Samba, compared to the
Windows box having its working copy on a fast local drive, that could
explain the difference.

Keep in mind that Subversion stores its working-copy metadata
currently in lots of little files in lots of .svn subdirectories in
every directory. Some svn operations are therefor very heavy on I/O.
E.g. for most operations (merge, update, commit, ...) the working copy
needs to be locked, and after the operation unlocked. This is done by
putting (and removing) little lock files in all those .svn
directories.

SVN's next release (1.7, slated for release late summer) will be much
better in this area, because its metadata will be centralized in one
single database at the root of the working copy.

Cheers,

-- 
Johan
Received on 2010-05-26 22:57:07 CEST

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.