[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: Erik Huelsmann <e.huelsmann_at_gmx.net>
Date: 2005-03-16 11:34:24 CET

> 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?

The time required to do a commit also has a lot to do with filesystem
performance of the filesystem on which your working copy is located.



DSL Komplett von GMX +++ SupergŁnstig und stressfrei einsteigen!
AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 16 11:39:46 2005

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.