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

Re: Repository size and performance

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2007-08-22 14:18:03 CEST

On 8/22/07, Banzi Massimo <massimo.banzi@telecomitalia.it> wrote:
> Hello
> We are migrating our development CM environment to subversion.
> Currently we have about a hundred projects and a thousand developers,
> and decided to install just one svn server (in high availability, with
> repository on SAN system , daily backed up, etc.).
> Authentication is managed through our company LDAP server.
> This decision (just one repo instead of several ones) was due to allow
> easier maintenance and tracking of the activities, since we also
> installed an ALM tool (Polarion).
> We also made a check on apache.org: apparently they use the same
> approach and their revision number is very high (over 550.000 revision.
> All this made us confident together with the fact that we can also
> improve our hardware if necessary.
> The performance of normal work are acceptable, but the use of certain
> useful features (eg. the revison graph that in a multi-branch env. is
> necessary ) is impossible.
> We noted it I use of Rev. graphs, but are there other analogue
> behaviours?
> Can you tell me if you found work around to this?

I presume you're talking about TortoiseSVN's revision graph? If so,
it's a known issue - the software has to go through the whole history
to build the graph, which obviously takes a while.

TSVN 1.5 will, from what I've read on the mailing list, cache this
data and will be *much* faster in building revision graphs. It'll be
released shortly after SVN 1.5 is released. There are also nightly
builds available which you can try out.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 22 14:15:46 2007

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.