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

Re: extreme slowness using smba + tortoise svn

From: Benjamin Smith-Mannschott <bsmith.occs_at_gmail.com>
Date: Tue, 2 Sep 2008 20:23:55 +0200

On Sep 2, 2008, at 20:08, Nathan Smith wrote:

> Hi,
> This is my first post to this list.
> I have been experiencing extreme slowness using Tortoise SVN and
> samba.
> For example, reverting takes between 5 and 10 minutes. Checking out
> the entire code base takes at least 90 minutes (co on linux takes
> less than 5 minutes). I have been trying to merge about 20 revisions
> from the trunk into a branch (we are using a broken trunk and
> working branches), and after an hour it has only merged 2 revisions.
> The code base is kind of large, but I have not really experienced
> issues like this using svn on the same code base in linux. In fact,
> using a shell on linux the changes seem nearly instantaneous or at
> least less than 30 seconds.
> I am checking the code out from a very powerful SVN server (3 cores,
> lots of ram, etc) to a weak/slow development webserver. Both the
> webserver and the SVN server are running smba. I could check out
> locally, but then I would have to sync from my local drive back out
> to the webserver, which is simply a hassle. Unfortunately, the
> webserver does not have svn installed.
> Editing files and performing normal operations across smba happens
> very quickly. It seems like it’s only the svn stuff that is slow. In
> fact, running top on both machines consistently shows 99% idle, even
> during “intense” svn operations.
> Does anyone have any suggestions on what I can do to speed up the
> process a little bit? Is there more information I can give to
> isolate any issues that exist in our setup?
> Thanks for your help,
> -Nate

Svn generates a *lot* of file system operations during checkout,
update or similar. I don't think they're asynchronous, so latency is
sure to be an issue. Networks have much higher latencies than local
hard disks. In your case the pain is doubled because you're getting it
coming (checking out from the svn server to your local machine) and
going (writing to the development web server via SMB).

Under these conditions, how could performance *not* suck?

I experimented along these lines once (keeping my working copies in an
eclipse workspace on an SMB share) and running eclipse locally under
windows. Boy did that stink. Running eclipse remotely and just
displaying it on the windows box is *much* *much* better!

// Ben
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-09-02 20:24:11 CEST

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