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

RE: Best Practices: Performance on Large Repositories?

From: Niklas Storm <niklas.storm_at_kreatel.se>
Date: 2005-03-16 09:25:42 CET

We have a rather large repository also. The branch I'm currently working on
contains about 44000 files, spread over a tree with a total of 9700
directories. The size of the data is about 1,2 GB.

A svn update or status normally takes somewhere between 10 seconds and 1,5
minutes, depending mostly on client load I think.

The client is a 2,4 GHz (somthing like that at least) Pentium IV RedHat 7.3.

The server is a dual Xeon 3,2 GHz RedHat ES with a FSFS repository. However,
before going into production with Subversion, we had a test server (Pentium
III 600 MHZ), and performance weren't much different then. Checkouts (and
other transactions involving lots of data) were slower though.

30 minutes to do a status/commit really seems way to much. Our developers
would go nuts under those circumstances;-)

/Niklas

> -----Original Message-----
> From: Steve Seremeth [mailto:subversion@seremeth.com]
> Sent: den 15 mars 2005 22:35
> To: users@subversion.tigris.org
> Subject: Best Practices: Performance on Large Repositories?
>
>
> Hello -
>
> We have a repository of about 11000 files totalling about 1200 MB. A
> commit or a status done at the trunk dir level takes as much as 30
> minutes whether using the svn command line (Windows XP or AIX) or
> Tortoise -- and seems to use very little CPU. Also, the
> server (RH ES 3
> on 2.4 Ghz Xeon using apache/berkeley db) just idles most of the time
> and seems to be doing nothing during any of these actions.
>
> What is the best way to improve performance? Since the
> server is idling
> I'm assuming it's not a software problem on the repository
> server. Are
> there benchmarks somewhere that we can look at to see how far off our
> setup is or is there anything we can do to semi-officially test
> performance against known good data?
>
> We end up doing a lot of "time svn commit trunk".
>
> Any advice would be greatly appreciated. If we're doing something
> wrong, that would be welcome news. If we are not doing
> something wrong,
> perhaps relative performance information should be posted in the FAQ?
>
> TIA -
>
> Steve
>
> P.S. I know we would be doing better if we were working on smaller
> pieces of the repository at any one time. No one interested in "cvs
> modules"-style functionality?
>
> ---------------------------------------------------------------------
> 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
Received on Wed Mar 16 09:28:32 2005

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