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

suggestions for large project (90K files, 930MB) - slow svn status

From: Tim Harvey <tim_harvey_at_yahoo.com>
Date: 2004-12-14 00:54:37 CET


I recently setup a subversion server and have been very happy with it. I'm
going to be working on a large project that has a tree of over 90K files making
up about 930MB. While I'll only be working in one or two subdirs, those dirs
are at the top of the tree. The project looks something like this:

    |- linux-2.0.x
    |- linux-2.4.x
    |- linux-2.6.x
    |- user

I'll be working a bit in the linux-2.4.x tree, and a lot in the user tree, but
will need to be performing my builds from the trunk. The linux-2.0.x and
linux-2.6.x trees are not really needed, but I would like to keep them in the
repository so that I can keep them up to date with new releases as I may use
them in the future. My work will be modifications to 'projectA', however
'projectA' will get peridic releases that I will want to merge in from time to

I ran a test where I created an FSFS repository and imported the tree. Doing a
'svn status' at the top of the tree takes 4 minutes, which is going to make it
fairly unusable for me. Does this 4 minutes sound right? Are there any
suggestions for how to layout a repository for this project?

I'm using a garden variety 1GHz x86 system with an IDE RAID5 array as my
server. I'm currently using the svn schema.

Thanks for any suggestions


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 14 00:59:39 2004

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.