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

RE: Speeding up workspace

From: Bert Huijben <rhuijben_at_sharpsvn.net>
Date: Tue, 10 Feb 2009 20:49:08 +0100

> -----Original Message-----
> From: Toby Thain [mailto:toby_at_telegraphics.com.au]
> Sent: Saturday, February 07, 2009 3:51 AM
> To: Bert Huijben
> Cc: Mark Phippard; Ruslan Sivak; users_at_subversion.tigris.org
> Subject: Re: Speeding up workspace
>
>
> On 6-Feb-09, at 6:44 PM, Bert Huijben wrote:
>
> > On Fri, Feb 6, 2009 at 10:37 PM, Mark Phippard <markphip_at_gmail.com>
> > wrote:
> >> On Fri, Feb 6, 2009 at 4:28 PM, Ruslan Sivak <russ_at_vshift.com>
> wrote:
> >>> Toby Thain wrote:
> >>>>
> >>>> Switch to Linux or OS X, which should be good for an immediate
> >>>> 10-20x
> >>>> speedup.
> >>>>
> >>>> --Toby
> >>>
> >>> Do you have any benchmarks to back this up?
> >>
> >> This isn't really Windows-bashing. The way SVN uses the local
> >> filesystem is just orders of magnitude faster on Linux and OSX.
> Here
> >> is a recent thread:
> >>
> >> http://svn.haxx.se/users/archive-2009-01/0326.shtml
> >>
> >> Back when I used to work on Windows, I would sometimes fire up Linux
> >> in VMWare to test some Subclipse feature in Linux. The
> >> performance of
> >> Eclipse/SVN in that Linux VM blew away Windows running natively as
> >> the
> >> host. The performance difference is frankly shocking.
> >
> > I think this is really is 'Windows bashing' unless you have explicit
> > numbers to prove it isn't.
>
> Jonathan Taylor posted numbers (16 Jan), and the speedup was
> confirmed by David Weintraub who moved his clients from Windows to
> Linux.

And I today I can confirm I found the cause of the 'svn update' slowdown.
The svn update time of an in my eyes gigantic working copy (207K files, 74K
directories/3 GB) drops by more than 80-90% if the Subversion locking
strategy changes in a system that writes less locking files (8234 lock files
in this case).
(Easy to implement by writing them following a smarter algorithm than one
per directory)

In Subversion 1.7 the entire locking mechanism as we use it in the current
working copy library will be removed and replaced with the new system
(already planned; implementation on its way on a branch)

For Subversion 1.6 (to be branched any time now) this new information is too
late :(

It won't be possible to do this in a patch or intermediate release following
our compatibility guarantees. As patch releases can't upgrade the working
copy format.

        Bert

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1135805

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-10 21:36:31 CET

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