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

RE: Problem performance TortoiseSVN

From: Loritsch, Berin <bloritsch_at_dtri.net>
Date: Wed, 15 Sep 2010 08:04:15 -0400

I know of a few things that can affect checkout/update performance that are not related to Tortoise SVN at all. They are related to how the file system works, and how the server is configured.

One of the strengths of Subversion is that its commits are atomic (all or nothing). That means that the client has to gather the current state of the working copy, check with the server if there are any subsequent changes, and then finally make the commit. Arguably, the first step in the process does produce the lion's share of the commit. Apparently, Subversion 1.7 is addressing this very issue.

The effects of the performance issues are made worse the larger the working copy is, and the more changes in the working copy between commits.

A peculiarity of Windows that also affects SVN (and consequently TortoiseSVN) is how the file system works with directories. Windows and Unix file systems are optimized very differently. On Windows, it is slower to traverse directories, and handles several files in the same directory much better than Unix. With Unix the story is reversed--faster to traverse directories and slower in directories with lots of files.

NOTE: this is at the file system level--the file explorer may add delays trying to present all the files to you. Bottom line is that if your project has a deep hierarchy of directories (which is required for Java projects) SVN will be held up by the Windows file system as it's trying to gather the current state of the local repository.

The server side configuration affects step number 2. Check out the SVN manual for more information on server side configuration:


Both of the things I presented here are things that Tortoise isn't responsible for, but can explain some of your frustrations. Every release of Windows changes how they cache files, and how long those files remain resident in memory. But with a base understanding of what can cause these slowdowns you might come up with alternative ways of improving performance without relying on the cache.

-----Original Message-----
From: BAILLIET Sebastien [mailto:Sebastien.BAILLIET_at_cimut.fr]
Sent: Wednesday, September 15, 2010 3:19 AM
To: users_at_tortoisesvn.tigris.org
Cc: CIMUT - Service Ingénierie Développement; NADAN Mael
Subject: Problem performance TortoiseSVN

Hi all,

We use TortoiseSVN and SVN since 4 years and for some time we meet problems of performance on the developers computers when update copy.
During the first update of working directory of developers it takes several minutes to make the operation of update, then during the day and following updates there is no more this deadline.

Have you an idea on the origin of the problem



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].

Confidentiality Note: The information contained in this message, and any attachments, may contain proprietary and/or privileged material. It is intended solely for the person or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-09-15 14:04:25 CEST

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