subversion is VERY slow

[Ruslan Sivak <rs...@istandfor.com>]

We have an app with about 15k files in it (and a bunch of folders).  When
this app is checked out as a working copy, it becomes 60k files and 30k
folders.   Needless to say, it becomes very slow to do anything on a global
level with this app, so we are forced to do individual commits from within
individual folders.  

 

We are also unable to do any sort of switching of branches as it would take
forever.  As it does to update the whole working copy (or do a checkout).  

 

I've set up a ram drive locally, and was able to do a checkout fairly quick.
I believe the disk access time is killing us when we are using subversion on
our development server.  

 

Is there a way to speed it up, short of setting up a ram drive on the
development and production servers?

 

Russ

Re: subversion is VERY slow

[Holger Hoffstaette <ho...@wizards.de>]

On Thu, 06 Apr 2006 08:13:59 -0500, Johnathan Gifford wrote:

> If you are on MS Windows, you also might be experiencing issues with
> indexing.  Go to the folder where you are creating your working copies,
> right click and choose properties.  There should be option somewhere to
> turn off 'Fast Indexing' (I'd give better details, but I'm on Mac).

Here's another one:
http://www.winguides.com/registry/display.php/50/

This has the same effect as mounting a Linux filesystem with the 'noatime'
option.

-h



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: subversion is VERY slow

[Johnathan Gifford <jg...@wernervas.com>]

If you are on MS Windows, you also might be experiencing issues with
indexing.  Go to the folder where you are creating your working copies,
right click and choose properties.  There should be option somewhere to turn
off 'Fast Indexing' (I'd give better details, but I'm on Mac).

Johnathan


On 4/6/06 7:49 AM, "Andy Levy" <an...@gmail.com> wrote:

> On 4/6/06, Ruslan Sivak <rs...@istandfor.com> wrote:
>> We have an app with about 15k files in it (and a bunch of folders).  When
>> this app is checked out as a working copy, it becomes 60k files and 30k
>> folders.   Needless to say, it becomes very slow to do anything on a global
>> level with this app, so we are forced to do individual commits from within
>> individual folders.
>> 
>> We are also unable to do any sort of switching of branches as it would take
>> forever.  As it does to update the whole working copy (or do a checkout).
>> 
>> I've set up a ram drive locally, and was able to do a checkout fairly quick.
>>  I believe the disk access time is killing us when we are using subversion
>> on our development server.
>> 
>> Is there a way to speed it up, short of setting up a ram drive on the
>> development and production servers?
> 
> On-access virus scanners are well-known to bog down local SVN
> operations, updates, etc. considerably.  If you're running one, tell
> it to ignore your working copy directory and see if performance
> improves.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: subversion is VERY slow

[Andy Levy <an...@gmail.com>]

On 4/6/06, Ruslan Sivak <rs...@istandfor.com> wrote:
> We have an app with about 15k files in it (and a bunch of folders).  When
> this app is checked out as a working copy, it becomes 60k files and 30k
> folders.   Needless to say, it becomes very slow to do anything on a global
> level with this app, so we are forced to do individual commits from within
> individual folders.
>
> We are also unable to do any sort of switching of branches as it would take
> forever.  As it does to update the whole working copy (or do a checkout).
>
> I've set up a ram drive locally, and was able to do a checkout fairly quick.
>  I believe the disk access time is killing us when we are using subversion
> on our development server.
>
> Is there a way to speed it up, short of setting up a ram drive on the
> development and production servers?

On-access virus scanners are well-known to bog down local SVN
operations, updates, etc. considerably.  If you're running one, tell
it to ignore your working copy directory and see if performance
improves.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org